Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Triggered write event for kvt #2351

Merged
merged 12 commits into from
Jun 13, 2024
Merged

Triggered write event for kvt #2351

merged 12 commits into from
Jun 13, 2024

Conversation

mjfh
Copy link
Contributor

@mjfh mjfh commented Jun 13, 2024

No description provided.

mjfh added 12 commits June 13, 2024 17:02
details:
  filter* => delta*
  roFilter => balancer
why:
  Might eventually fail if re-centring is blocked. Some logic will be
  added in subsequent patch sets.
why:
  All previously used CFs must be declared when re-opening an existing
  database.
…eters

why:
  Opening a set column families (with different open options) must span
  at least the ones that are already on disk.
why:
  This allows to save data from a guest application (think `KVT`) to
  get synced with the write cycle so the guest and `Aristo` save all
  atomically.
why:
  Some systems (i.p `fluffy` and friends) use the `Aristo` memory
  backend emulation and do not link against rocksdb when building the
  application. So this should fix that problem.
@mjfh mjfh merged commit 5a5cc62 into master Jun 13, 2024
26 checks passed
@mjfh mjfh deleted the triggered-write-event-for-kvt branch June 13, 2024 18:15
@@ -28,6 +28,7 @@ type
Ooops
AristoDbMemory ## Memory backend emulator
AristoDbRocks ## RocksDB backend
AristoDbDualRocks ## Dual RocksDB backends for `Kvt` and `Aristo`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's not add another backend - we should be running tests in the environment exactly how they will appear in production and this looks like a trap for synchronization bugs because of the non-atomicity between updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants