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

Extend FAQ #1388

Merged
merged 5 commits into from
Jun 23, 2022
Merged

Extend FAQ #1388

merged 5 commits into from
Jun 23, 2022

Conversation

PSeitz
Copy link
Contributor

@PSeitz PSeitz commented Jun 15, 2022

No description provided.

@PSeitz
Copy link
Contributor Author

PSeitz commented Jun 15, 2022

Not sure if this is the best place for this.

@PSeitz PSeitz requested review from maximkpa and fulmicoton June 15, 2022 05:57
@codecov-commenter
Copy link

codecov-commenter commented Jun 15, 2022

Codecov Report

Merging #1388 (f7f15de) into main (83d0c13) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1388   +/-   ##
=======================================
  Coverage   94.29%   94.29%           
=======================================
  Files         236      236           
  Lines       43418    43418           
=======================================
  Hits        40942    40942           
  Misses       2476     2476           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 83d0c13...f7f15de. Read the comment docs.

README.md Outdated

### When will my documents be searchable during indexing?
- Documents will be searchable after a `commit`. A commit can be executed manually, or when reaching the memory budget during indexing. Comitting means the segment will be flushed to disk.
Copy link
Collaborator

Choose a reason for hiding this comment

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

That's incorrect.

A commit can only be done manually.

Segment getting serialized to disk can happen when we reach the memory budget, but the data will not be made searchable until a manual commit is done.

It might be important to also add that existing reader's need to be reload for changes to be visible.

Copy link
Contributor

Choose a reason for hiding this comment

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

Documents will be searchable after a commit, which can only be done manually. When reaching the memory budget during indexing, a segment can get serialized to disk, but the data will not be searchable until a commit is done (not necessary to repeat "manual commit" here imo). It is important to reload the existing reader for changes to be visible.

Copy link
Collaborator

@fulmicoton fulmicoton left a comment

Choose a reason for hiding this comment

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

see comment

README.md Outdated Show resolved Hide resolved
@fulmicoton fulmicoton merged commit 93f356a into main Jun 23, 2022
@fulmicoton fulmicoton deleted the PSeitz-patch-1 branch June 23, 2022 02:53
This was referenced Jan 13, 2023
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.

4 participants