You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
156854: api: allow admin user to view databases metadata r=jasonlmfong a=jasonlmfong
the admin user currently has no view into all the databases due to its non-existence in the role_members table, this change adds a third condition to the where clause to allow the view
Epic: None
Release: None
-----
api: refactor query logic for get databases metadata
pull the left join condition on role_members out into the where clause
Epic: None
Release: None
158011: *: clarify log/state engine use r=arulajmani a=pav-kv
This PR is one in the series of PRs clarifying the use of `storage.Engine`: whether it is the raft/log or state machine engine.
Here we solidify that:
- The sideloaded entry files are stored in the state engine `FS`. These are to be ingested into the state engine when the corresponding entry is applied.
- Store liveness uses `LogEngine` because it needs a timely sync. More generally (in upcoming PRs), all `Store`-local keys are in the log engine.
- Node liveness compactions in `startPeriodicLivenessCompaction` correctly use the `StateEngine` (works in the MVCC span). Just a drive-by style fixup.
Epic: CRDB-55220
Co-authored-by: Jason Fong <[email protected]>
Co-authored-by: Pavel Kalinnikov <[email protected]>
0 commit comments