-
Notifications
You must be signed in to change notification settings - Fork 616
Add documentation for agentic search processors #11117
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
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
Introduced 3.3 | ||
{: .label .label-purple } | ||
|
||
The `agentic_context` search response processor adds agent execution context information to search response extensions. This processor works in conjunction with the [agentic query translator]({{site.url}}{{site.baseurl}}/search-plugins/agentic-query-translator/) to provide transparency into the agent's query translation process and maintain conversation continuity. |
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.
Please verify the links in the doc
3b9439b
to
1d7b46c
Compare
Signed-off-by: Owais <[email protected]>
1d7b46c
to
6ac3aaf
Compare
Signed-off-by: Fanit Kolchina <[email protected]>
Signed-off-by: Fanit Kolchina <[email protected]>
_query-dsl/specialized/index.md
Outdated
|
||
- [`script_score`]({{site.url}}{{site.baseurl}}/query-dsl/specialized/script-score/): Calculates a custom score for matching documents using a script. | ||
|
||
- `template`: Allows you to use mustache templating in queries. |
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.
Is this related to agentic search?
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.
Added by @kolchfa-aws. Removed
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.
Please add this back: while I was adding the query type, I noticed that the template query is not listed on the index page.
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.
Ah! I see. Adding it back
:--- | :--- | :--- | ||
`agent_steps_summary` | Boolean | Whether to include the agent's execution steps summary in the response. Default is `false`. Optional. | ||
`dsl_query` | Boolean | Whether to include the generated DSL query in the response. Default is `false`. Optional. | ||
|
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.
How is memory ID provided? Do we need to mention that memory ID will always be provided as long as this response processor is added?
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.
Memory id is not provided in the processor but in the query side. Can be taken care in the agentic search doc PR. I can add about the response that memory id would be present always
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.
Overall looks good to me!
Signed-off-by: Owais <[email protected]>
6f031b9
to
b503cc1
Compare
Signed-off-by: kolchfa-aws <[email protected]>
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.
Editorial review
_search-plugins/search-pipelines/agentic-query-translator-processor.md
Outdated
Show resolved
Hide resolved
_search-plugins/search-pipelines/agentic-query-translator-processor.md
Outdated
Show resolved
Hide resolved
_search-plugins/search-pipelines/agentic-query-translator-processor.md
Outdated
Show resolved
Hide resolved
_search-plugins/search-pipelines/agentic-query-translator-processor.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Nathan Bower <[email protected]>
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.
LGTM
Description
Add documentation for agentic search processors
Issues Resolved
Part of #11026
Version
3.3
Frontend features
If you're submitting documentation for an OpenSearch Dashboards feature, add a video that shows how a user will interact with the UI step by step. A voiceover is optional.
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.