-
Notifications
You must be signed in to change notification settings - Fork 25
make genesis respect the config flag for disable_persistence #1902
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
base: main
Are you sure you want to change the base?
Conversation
| log_info(format!( | ||
| "Job Results :: Persisted to dB: batch-id={batch_id}" | ||
| )); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note that this log was removed. it seems redundant.
| log_info(format!( | ||
| "Job Results :: Persisted to dB: modification_id={modification_id}" | ||
| )); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR adds support for the disable_persistence configuration flag in the genesis indexing process to enable testing without database writes. The changes introduce conditional logic to skip database operations when persistence is disabled while maintaining in-memory processing.
Key changes:
- Added conditional checks around all database persistence operations (backup, modifications table cleanup, batch/modification persistence)
- Updated logging to indicate when operations are skipped due to disabled persistence
- Added persistence status to startup logging and warning when using backup source with persistence disabled
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
testing found that changes are still getting persisted. needs fixing. |
06e5856 to
d04250e
Compare
I found that my genesis tests on the dev cluster inserted the irises and graph links into the CPU database instead of just keeping them in memory (when
SMPC__DISABLE_PERSISTENCEwastrue). we don't really need this flag for production but not having it makes testing significantly more difficult because i would then have to either delete items from the graph or add more irises to the GPU database.This PR adds a separate code path to allow testing without persistence.