Update ESQL for Search landing page, tutorial for 9.1 #1797
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
|
🔍 Preview links for changed docs: 🔔 The preview site may take up to 3 minutes to finish building. These links will become live once it completes. |
carlosdelest
reviewed
Jul 1, 2025
|
Thanks Carlos addressed all in latest commit |
🔍 Preview links for changed docs |
ioanatia
approved these changes
Jul 7, 2025
kosabogi
approved these changes
Jul 7, 2025
| ::::{important} | ||
| These queries match documents but don't automatically sort by relevance. To get the most relevant results first, you need to use `METADATA _score` and sort by score. See [Relevance scoring](#esql-for-search-scoring) for more information. | ||
| :::: | ||
| Use the [`MATCH_PHRASE` function](elasticsearch://reference/query-languages/esql/functions-operators/search-functions.md#esql-match_phrase) to perform a `match_phrase` query on the specified field. This is equivalent to using the [match_phrase query](elasticsearch://reference/query-languages/query-dsl/query-dsl-match-query-phrase.md) in Query DSL. |
There was a problem hiding this comment.
Suggested change
| Use the [`MATCH_PHRASE` function](elasticsearch://reference/query-languages/esql/functions-operators/search-functions.md#esql-match_phrase) to perform a `match_phrase` query on the specified field. This is equivalent to using the [match_phrase query](elasticsearch://reference/query-languages/query-dsl/query-dsl-match-query-phrase.md) in Query DSL. | |
| Use the [`MATCH_PHRASE` function](elasticsearch://reference/query-languages/esql/functions-operators/search-functions.md#esql-match_phrase) to perform a `match_phrase` query, equivalent to the [match_phrase query](elasticsearch://reference/query-languages/query-dsl/query-dsl-match-query-phrase.md) in Query DSL. |
| | WHERE semantic_content: "What are the impacts of climate change on agriculture?" | ||
| | SORT _score DESC | ||
| ``` | ||
| Refer to [semantic search with semantic_text](/solutions/search/semantic-search/semantic-search-semantic-text.md) for an example or follow the [tutorial](esql-search-tutorial.md#step-5-semantic-search-and-hybrid-search). |
There was a problem hiding this comment.
Suggested change
| Refer to [semantic search with semantic_text](/solutions/search/semantic-search/semantic-search-semantic-text.md) for an example or follow the [tutorial](esql-search-tutorial.md#step-5-semantic-search-and-hybrid-search). | |
| For an example, see [semantic search with semantic_text](/solutions/search/semantic-search/semantic-search-semantic-text.md) or follow the [semantic search tutorial](esql-search-tutorial.md#step-5-semantic-search-and-hybrid-search). |
| Use the [KQL function](elasticsearch://reference/query-languages/esql/functions-operators/search-functions.md#esql-kql) to use the [Kibana Query Language](/explore-analyze/query-filter/languages/kql.md) in your {{esql}} queries. | ||
|
|
||
| You can perform semantic searches over [`semantic_text`](elasticsearch://reference/elasticsearch/mapping-reference/semantic-text.md) field types using the same match syntax as full-text search. | ||
| For migrating queries from other Kibana interfaces, the `KQL` function preserves existing query syntax and allows gradual migration to {{esql}} without rewriting existing Kibana queries. |
There was a problem hiding this comment.
Not sure of the word "interfaces".
Suggested change
| For migrating queries from other Kibana interfaces, the `KQL` function preserves existing query syntax and allows gradual migration to {{esql}} without rewriting existing Kibana queries. | |
| If you are familiar with other query languages in Kibana before, the `KQL` function preserves existing query syntax and allows gradual migration to {{esql}} without rewriting existing Kibana queries. |
| ## Limitations [esql-for-search-limitations] | ||
|
|
||
| Refer to [{{esql}} limitations](elasticsearch://reference/query-languages/esql/limitations.md#esql-limitations-full-text-search) for a list of known limitations. | ||
| Refer to [hybrid search with semantic_text](hybrid-semantic-text.md) for an example or follow the [tutorial](esql-search-tutorial.md#step-5-semantic-search-and-hybrid-search). |
There was a problem hiding this comment.
same comment as before.
|
|
||
| :::{tip} | ||
| {{esql}} provides two ways to perform full-text searches: | ||
| {{esql}} provides multiple functions for full-text search, including `MATCH`, `MATCH_PHRASE`, and `QSTR`. For basic text matching, you can use either: |
There was a problem hiding this comment.
Suggested change
| {{esql}} provides multiple functions for full-text search, including `MATCH`, `MATCH_PHRASE`, and `QSTR`. For basic text matching, you can use either: | |
| {{esql}} provides multiple functions for full-text search, including `MATCH`, `MATCH_PHRASE`, and `QSTR`. For basic text matching, you can use one of the following: |
| {{esql}} provides two ways to perform full-text searches: | ||
| {{esql}} provides multiple functions for full-text search, including `MATCH`, `MATCH_PHRASE`, and `QSTR`. For basic text matching, you can use either: | ||
|
|
||
| 1. Full [match function](elasticsearch://reference/query-languages/esql/functions-operators/search-functions.md#esql-match) syntax: `match(field, "search terms")` |
There was a problem hiding this comment.
could replace with bullets instead of numbered sequence.
leemthompo
added a commit
to elastic/elasticsearch
that referenced
this pull request
Jul 24, 2025
8.19 equivalent of elastic/docs-content#1797
leemthompo
added a commit
to elastic/elasticsearch
that referenced
this pull request
Jul 25, 2025
8.19 equivalent of elastic/docs-content#1797
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
9.x portion of https://github.com/elastic/developer-docs-team/issues/300
Contains updates to:
landing page changes:
• reorganized around user journey - overview → concepts → functions → advanced flow
• removed code examples - directs to tutorial and reference docs instead of duplicating content
• grouped related functionality - consolidated search functions under clear sections
• focused on orientation - helps users understand capabilities and find next steps
• reduced maintenance - fewer duplicated explanations across multiple pages
tutorial changes:
• restructured steps for logical progression
• expanded section 3 into two focused steps
• added new advanced features section
• improved step titles
• simplified next steps