Skip to content

Conversation

thekofimensah
Copy link
Contributor

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/

Copy link

cla-checker-service bot commented Jan 9, 2025

💚 CLA has been signed

Copy link
Contributor

github-actions bot commented Jan 9, 2025

Documentation preview:

@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label v8.17.2 external-contributor Pull request authored by a developer outside the Elasticsearch team labels Jan 9, 2025
@shainaraskas shainaraskas added >docs General docs changes v9.0.0 v8.18.0 labels Jan 9, 2025
@shainaraskas shainaraskas self-requested a review January 9, 2025 13:35
@elasticsearchmachine elasticsearchmachine added the Team:Docs Meta label for docs team label Jan 9, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-docs (Team:Docs)

@elasticsearchmachine elasticsearchmachine removed the needs:triage Requires assignment of a team area label label Jan 9, 2025
@shainaraskas shainaraskas added the needs:triage Requires assignment of a team area label label Jan 9, 2025
@elasticsearchmachine elasticsearchmachine removed the needs:triage Requires assignment of a team area label label Jan 9, 2025
@shainaraskas shainaraskas self-assigned this Jan 9, 2025
@shainaraskas
Copy link
Contributor

@elasticmachine test this please

@shainaraskas shainaraskas requested review from georgewallace and removed request for shainaraskas January 9, 2025 21:39
@shainaraskas shainaraskas removed their assignment Jan 9, 2025
@shainaraskas
Copy link
Contributor

run docs-build

Copy link
Contributor

@georgewallace georgewallace left a 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.

thekofimensah and others added 3 commits January 9, 2025 17:46
Co-authored-by: George Wallace <[email protected]>
Co-authored-by: George Wallace <[email protected]>
@thekofimensah
Copy link
Contributor Author

run docs-build

@leemthompo leemthompo added the auto-backport Automatically create backport pull requests when merged label Jan 10, 2025
@leemthompo
Copy link
Contributor

leemthompo commented Jan 10, 2025

@thekofimensah (for future reference) we recommend opening PRs against main branch, which makes it easier to reason about backports to other versions, and the backport PRs will automerge once they pass CI :)

@georgewallace georgewallace enabled auto-merge (squash) January 10, 2025 14:57
@leemthompo
Copy link
Contributor

leemthompo commented Jan 10, 2025

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)

@thekofimensah
Copy link
Contributor Author

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.

@leemthompo
Copy link
Contributor

@elasticsearchmachine test this

@leemthompo
Copy link
Contributor

run docs-build

@leemthompo
Copy link
Contributor

@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 elastic/docs repo.

@georgewallace georgewallace merged commit 6c28b7f into elastic:8.17 Jan 13, 2025
6 of 7 checks passed
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
main
8.x

georgewallace added a commit to georgewallace/elasticsearch that referenced this pull request Jan 13, 2025
* 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 added a commit to georgewallace/elasticsearch that referenced this pull request Jan 13, 2025
* 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]>
@leemthompo
Copy link
Contributor

leemthompo commented Jan 13, 2025

@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

elasticsearchmachine pushed a commit that referenced this pull request Jan 13, 2025
leemthompo pushed a commit that referenced this pull request Jan 13, 2025
martijnvg pushed a commit to martijnvg/elasticsearch that referenced this pull request Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged >docs General docs changes external-contributor Pull request authored by a developer outside the Elasticsearch team Team:Docs Meta label for docs team v8.17.2 v8.18.0 v9.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants