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 force_merge API #5057

Closed
1 of 4 tasks
andrross opened this issue Sep 20, 2023 · 0 comments · Fixed by #5768
Closed
1 of 4 tasks

[DOC] Document the force_merge API #5057

andrross opened this issue Sep 20, 2023 · 0 comments · Fixed by #5768
Assignees
Labels
3 - Done Issue is done/complete Content gap

Comments

@andrross
Copy link
Member

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.

The documentation is relevant for all versions of OpenSearch going back to 1.0.

We have some documentation of force merge for the index management plugin:

However, we should have comprehensive documentation for the underlying REST API, e.g. POST /<index>/_forcemerge. A subject matter expert will need to write up this documentation, but I'm creating this placeholder issue for now.

What other resources are available?

Issue 7644 in OpenSearch changes some subtle behavior of one option of this API. I couldn't find existing documentation for this API to update, so we should probably create it :)

@Naarcha-AWS Naarcha-AWS added 1 - Backlog Issue: The issue is unassigned or assigned but not started good first issue Good for newcomers and removed untriaged labels Oct 16, 2023
@kolchfa-aws kolchfa-aws added the 2 - In progress Issue/PR: The issue or PR is in progress. label Dec 7, 2023
@hdhalter hdhalter added 3 - Done Issue is done/complete and removed good first issue Good for newcomers 1 - Backlog Issue: The issue is unassigned or assigned but not started 2 - In progress Issue/PR: The issue or PR is in progress. labels Jul 19, 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 Content gap
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants