-
-
Notifications
You must be signed in to change notification settings - Fork 28
Expose Ingestion API with Inversion of Control #191
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?
Expose Ingestion API with Inversion of Control #191
Conversation
a043736 to
14ef584
Compare
|
I'm currently massively simplifying the flush logic such that is gets really easy to flush active and sealed memtables in one go by just calling |
|
(Forgot to submit comments) But as I said, I am currently changing the Flush API which should make the ingestion API much simpler. (WIP at #194) |
1af202a to
87c7d03
Compare
87c7d03 to
36b2651
Compare
| false, | ||
| false, |
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.
I forgot to document this - but I purposefully avoided using the config for pinning because when you ingest a very large database it is assigned to L1 and will pin all those blocks which could provoke OOM.
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.
updated
resolve #190