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
Kuzu currently lacks an atomic export operation to create a full database backup while allowing writes to continue. This feature would be useful for use cases such as event-sourced architectures, where backups need to be taken at a specific event index to enable point-in-time recovery.
Use Case:
In an event-sourced system, all writes to Kuzu are synchronized through an event log.
During a backup, it's crucial to capture the exact event index to enable deterministic recovery.
A feature similar to SQLite's Backup API would allow creating a consistent database snapshot without stopping writes.
Proposed Solution:
Implement a mechanism to clone or export the entire database atomically.
Ensure that the snapshot remains consistent even if writes occur during the operation. Or automatically pause all writes on the SDK layer so the client code doesn't need to worry about locking.
Provide an API to initiate and manage such a backup process.
The text was updated successfully, but these errors were encountered:
API
Node.js
Description
Kuzu currently lacks an atomic export operation to create a full database backup while allowing writes to continue. This feature would be useful for use cases such as event-sourced architectures, where backups need to be taken at a specific event index to enable point-in-time recovery.
Use Case:
Proposed Solution:
The text was updated successfully, but these errors were encountered: