-
Notifications
You must be signed in to change notification settings - Fork 427
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add an option to force or wait for commit #2995
Add an option to force or wait for commit #2995
Conversation
Adds an option to force a commit or wait for the next commit while issuing an ingest command. This commit only implements it for the ingest endpoint. If all records in the batch fail, the command will hang until at least one good document is indexed until quickwit-oss#2825 is merged in or the document parsing is moved to the early stages. See quickwit-oss#2699
@trinity-1686a can you have a look? |
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.
It would be nice to have an e2e style integration test that ingest a few docs forcing commit and immediately search for them, but that'll possibly be best done once #2984 has been worked on
Let's wait for 0.5 release before merging. |
As much as release branches can be a pain, the balance of cost vs benefit of having them will only move towards the benefit as the team and customer base grow. Maybe be something to consider for 0.6? |
@imotov absolutely, we are releasing tomorrow so we can merge your PR tomorrow. |
0.5.0 has been released. I'm going to merge |
Description
Adds an option to force a commit or wait for the next commit while issuing an ingest command. This commit only implements it for the ingest endpoint. If all records in the batch fail, the command will hang until at least one good document is indexed until #2826 is merged in or the document parsing is moved to the early stages.
See #2699
How was this PR tested?
Added tests.