-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Adjustments to match Opster, readability #119812
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
Conversation
💚 CLA has been signed |
Documentation preview: |
Pinging @elastic/es-docs (Team:Docs) |
@elasticmachine test this please |
run docs-build |
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.
Made a couple suggestions to the content.
Co-authored-by: George Wallace <[email protected]>
Co-authored-by: George Wallace <[email protected]>
run docs-build |
@thekofimensah (for future reference) we recommend opening PRs against |
FYI updating branch is rarely a requirement, unless you have conflicts, or wanna retrigger CI due to failures (e.g. broken links that merging upstream will fix) |
Yeah I'm not sure why I can't merge it in the current state, good to know that updating the branch wouldn't do much. |
@elasticsearchmachine test this |
run docs-build |
@thekofimensah as external contributor we have to trigger CI manually every time. I recommend, as much as possible, building docs locally :). Get started by cloning the |
* Adjustments to match Opster, readability https://opster.com/guides/elasticsearch/search-apis/elasticsearch-bool-queries/ * Edits Co-authored-by: George Wallace <[email protected]> * Spacing Co-authored-by: George Wallace <[email protected]> --------- Co-authored-by: George Wallace <[email protected]>
* Adjustments to match Opster, readability https://opster.com/guides/elasticsearch/search-apis/elasticsearch-bool-queries/ * Edits Co-authored-by: George Wallace <[email protected]> * Spacing Co-authored-by: George Wallace <[email protected]> --------- Co-authored-by: George Wallace <[email protected]>
@georgewallace I just noticed that this auto-merged before docs build check passed which is a weird and bad side effect of the external contributor dynamics |
* Adjustments to match Opster, readability https://opster.com/guides/elasticsearch/search-apis/elasticsearch-bool-queries/ * Edits * Spacing --------- Co-authored-by: Kofi B <[email protected]>
* Adjustments to match Opster, readability https://opster.com/guides/elasticsearch/search-apis/elasticsearch-bool-queries/ * Edits * Spacing --------- Co-authored-by: Kofi B <[email protected]>
…0031) * Adjustments to match Opster, readability https://opster.com/guides/elasticsearch/search-apis/elasticsearch-bool-queries/ * Edits * Spacing --------- Co-authored-by: Kofi B <[email protected]>
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/