Skip to content
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

[DOC] document the nested_path parameter in agent search tools #7740

Closed
1 of 4 tasks
zhichao-aws opened this issue Jul 17, 2024 · 1 comment · Fixed by #7741
Closed
1 of 4 tasks

[DOC] document the nested_path parameter in agent search tools #7740

zhichao-aws opened this issue Jul 17, 2024 · 1 comment · Fixed by #7741
Assignees
Labels
3 - Done Issue is done/complete v2.16.0

Comments

@zhichao-aws
Copy link
Member

zhichao-aws commented Jul 17, 2024

What do you want to do?
Per customer request, in 2.16 we will support nested field in agent search tools (neural sparse tool, vectorDB tool, RAG Tool). We add a new parameter to these tools, and we need to document this change

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request. Provide a summary of the request.

*Version: List the OpenSearch version to which this issue applies, e.g. 2.14, 2.12--2.14, or all.
2.16
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
opensearch-project/skills#350

@zhichao-aws
Copy link
Member Author

Please assign this issue to me

@hdhalter hdhalter added v2.16.0 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. and removed untriaged labels Jul 17, 2024
@hdhalter hdhalter added 2 - In progress Issue/PR: The issue or PR is in progress. and removed 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. labels Jul 17, 2024
@hdhalter hdhalter added 3 - Done Issue is done/complete and removed 2 - In progress Issue/PR: The issue or PR is in progress. labels Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Done Issue is done/complete v2.16.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants