Skip to content

Conversation

@leemthompo
Copy link
Contributor

@leemthompo leemthompo commented Nov 18, 2025

Closes elastic/docs-content#3250

Note

It's probably easier to review this by running through the URL preview, rather than inspecting the diff, because the flow has changed significantly. :)

The goal of this tutorial is mainly to pull together the capabilities mentioned on the ESQL for search overview page into concrete examples. It's not a realistic use case tutorial, it's more about demonstrating functionalities. But in the future we could consider chunking this into more targeted tutorials and using less toylike data sets. That's a discussion for a follow-up.

Check out the URL preview

Summary

  • Add FORK/FUSE hybrid search with RRF
  • Add RERANK for semantic reranking
  • Add COMPLETION for LLM text generation
  • Add KNN/TEXT_EMBEDDING for vector search
  • Reorganize steps for better logical flow (FTS → filtering → combining → AI)
  • Use approach-based tabs for hybrid search (OR vs FORK/FUSE)
  • Update title to 'ES|QL for search tutorial'

- Add FORK/FUSE hybrid search with RRF
- Add RERANK for semantic reranking
- Add COMPLETION for LLM text generation
- Add KNN/TEXT_EMBEDDING for vector search
- Reorganize steps for better logical flow (FTS → filtering → combining → AI)
- Fix QSTR, RERANK, COMPLETION syntax
- Use approach-based tabs for hybrid search (OR vs FORK/FUSE)
- Add callout annotations with numbered list explanations
- Update title to 'ES|QL for search tutorial'
@github-actions
Copy link
Contributor

github-actions bot commented Nov 18, 2025

🔍 Preview links for changed docs

@github-actions

This comment was marked as outdated.

Copy link
Contributor

@ioanatia ioanatia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks great! left a few comments

| WHERE description:"vegetarian recipes" <1>
| SORT _score DESC
| LIMIT 100 <2>
| RERANK "healthy quick meals" ON description WITH { "inference_id": "my_reranker_model" } <3>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would remove WITH { "inference_id": "my_reranker_model" } to simplify the example - and we can say in the explanation that we use the default rerank model that we have available (e.g. Elastic rerank).
we can also mention that you can configure RERANK to work with another model, by pointing the user to the RERANK docs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perfect, makes sense

Copy link
Contributor Author

@leemthompo leemthompo Nov 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@afoucret I guess we need to update the RERANK reference doc to explain how defaults work too... creating an issue

@dustincoates
Copy link

Not the main point of the update, but maybe worthwhile to take this opportunity to update the errant code highlighting of the colon on line 154?
image

@dustincoates
Copy link

Not the main point of the update, but maybe worthwhile to take this opportunity to update the errant code highlighting of the colon on line 154? image

Nevermind, I see now that it's not a formatting error, it just wasn't clear when I read it.

@leemthompo
Copy link
Contributor Author

Nevermind, I see now that it's not a formatting error, it just wasn't clear when I read it.

yeah it's such a compact operator that it's hard to inline it nicely, I might wrap it in quotes just so it stands out better :)

@leemthompo leemthompo marked this pull request as ready for review November 25, 2025 16:28
@elasticsearchmachine elasticsearchmachine added the needs:triage Requires assignment of a team area label label Nov 25, 2025
@leemthompo leemthompo added the >docs General docs changes label Nov 25, 2025
@elasticsearchmachine elasticsearchmachine added Team:Docs Meta label for docs team and removed needs:triage Requires assignment of a team area label labels Nov 25, 2025
@elasticsearchmachine
Copy link
Collaborator

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

@leemthompo
Copy link
Contributor Author

@ioanatia thanks for the review, I've addressed all your suggestions

@leemthompo leemthompo requested a review from ioanatia November 26, 2025 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>docs General docs changes Team:Docs Meta label for docs team v9.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update ESQL for search pages for 9.2

4 participants