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] Concurrent segment search support for composite aggs without scripting #6929

Closed
1 of 4 tasks
jed326 opened this issue Apr 9, 2024 · 2 comments · Fixed by #7043
Closed
1 of 4 tasks

[DOC] Concurrent segment search support for composite aggs without scripting #6929

jed326 opened this issue Apr 9, 2024 · 2 comments · Fixed by #7043
Assignees
Labels
3 - Done Issue is done/complete v2.14.0
Milestone

Comments

@jed326
Copy link
Contributor

jed326 commented Apr 9, 2024

What do you want to do?

  • 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 and all versions that are affected.
For 2.14 we should update https://opensearch.org/docs/latest/search-plugins/concurrent-segment-search/#limitations to indicate that composite aggs now do support concurrent segment search but only when scripting is not used.

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

@hdhalter hdhalter added 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. v2.14.0 and removed untriaged labels Apr 9, 2024
@hdhalter hdhalter added this to the v2.14 milestone Apr 9, 2024
@hdhalter
Copy link
Contributor

Hi @jed326 , what is your ETA for producing the doc PR? To meet entrance criteria, the PR must be open and in review by 4/30. Thanks!

@jed326
Copy link
Contributor Author

jed326 commented Apr 25, 2024

Thanks for the reminder @hdhalter. I was waiting to see if I would be able to get the second issue in before 2.14 release but doesn't look like that's happening so I will open a PR for this soon.

@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 Apr 29, 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 Apr 30, 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.14.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants