[Docs] Correct max_doc_freq default value
#49536
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The default is set to Integer.MAX_VALUE but is reported to be `0` in the docs. With the current implementation a value of 0 would mean all terms are filtered out, which is the opposite of "unbounded". Closes elastic#49520
cbuescher
added
>docs
Collaborator
|
Pinging @elastic/es-search (:Search/Search) |
Collaborator
|
Pinging @elastic/es-docs (>docs) |
cbuescher
pushed a commit
that referenced
this pull request
Nov 26, 2019
The default is set to Integer.MAX_VALUE but is reported to be `0` in the docs. With the current implementation a value of 0 would mean all terms are filtered out, which is the opposite of "unbounded". Closes #49520
cbuescher
pushed a commit
that referenced
this pull request
Nov 26, 2019
The default is set to Integer.MAX_VALUE but is reported to be `0` in the docs. With the current implementation a value of 0 would mean all terms are filtered out, which is the opposite of "unbounded". Closes #49520
cbuescher
pushed a commit
that referenced
this pull request
Nov 26, 2019
The default is set to Integer.MAX_VALUE but is reported to be `0` in the docs. With the current implementation a value of 0 would mean all terms are filtered out, which is the opposite of "unbounded". Closes #49520
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The default is set to Integer.MAX_VALUE but is reported to be
0in the docs.With the current implementation a value of 0 would mean all terms are filtered
out, which is the opposite of "unbounded".
Closes #49520