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

Add wait_for_completion parameter to the documents of shrink, clone, split, open, and forcemerge APIs #3664

Open
gaobinlong opened this issue Mar 31, 2023 · 2 comments
Labels
1 - Backlog Issue: The issue is unassigned or assigned but not started Sev3 Medium priority. Content that's missing, driven by dev, PM or the community. v2.0.0 v2.1.0 v2.2.0 v2.3.0 v2.4.0 'Issues and PRs related to version v2.4.0' v2.5.0 'Issues and PRs related to version v2.5.0' v2.6.0 v2.7.0

Comments

@gaobinlong
Copy link
Contributor

Is your feature request related to a problem? Please describe.
In PR opensearch-project/OpenSearch#6434, we introduced a new request parameter wait_for_completion for the shrink, clone, split, open, and forcemerge APIs, we need to document it.

Describe the solution you'd like
Add some description for the parameter wait_for_completion in the documents of shrink, clone, split, open, and forcemerge APIs, just like reindex API, we can refer to the description of the same parameter in reindex API's document.

@gaobinlong gaobinlong added enhancement New feature or request untriaged labels Mar 31, 2023
@krisfreedain
Copy link
Member

Hello @gaobinlong - I believe this issue should be moved to the https://github.com/opensearch-project/documentation-website repo (cc @hdhalter )

@nknize nknize transferred this issue from opensearch-project/project-website Apr 4, 2023
@Naarcha-AWS Naarcha-AWS added 1 - Backlog Issue: The issue is unassigned or assigned but not started v2.0.0 v2.1.0 v2.2.0 v2.3.0 v2.4.0 'Issues and PRs related to version v2.4.0' v2.5.0 'Issues and PRs related to version v2.5.0' v2.6.0 v2.7.0 Sev3 Medium priority. Content that's missing, driven by dev, PM or the community. and removed enhancement New feature or request untriaged labels Apr 18, 2023
@gaobinlong
Copy link
Contributor Author

@Naarcha-AWS the functionality will be released in 2.7, and will not be backported to old version, so can you help to remove some labels like v2.3.0, v2.4.0 for this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Backlog Issue: The issue is unassigned or assigned but not started Sev3 Medium priority. Content that's missing, driven by dev, PM or the community. v2.0.0 v2.1.0 v2.2.0 v2.3.0 v2.4.0 'Issues and PRs related to version v2.4.0' v2.5.0 'Issues and PRs related to version v2.5.0' v2.6.0 v2.7.0
Projects
None yet
Development

No branches or pull requests

3 participants