Adjustments to match Opster, readability #119812
Open
+9
−6
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.
Part of the logic of rearranging the order of the different clauses is that must_not + filter and must + should are more related and it makes sense in my opinion to order them by most similar, but this may be up to debate.
Also thought that this page was a bit general and I wanted to make it more explicit about which clauses are used for what and why.
This is part of the effort to bring in opster documentation to elastic.
https://opster.com/guides/elasticsearch/search-apis/elasticsearch-bool-queries/