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 usage clearly about update operation with ingest pipeline #8791

Open
1 of 4 tasks
gaobinlong opened this issue Nov 21, 2024 · 2 comments
Open
1 of 4 tasks
Assignees
Labels
1 - Backlog - DEV Developer assigned to issue is responsible for creating PR.

Comments

@gaobinlong
Copy link
Contributor

gaobinlong commented Nov 21, 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.

The update document API doesn't support pipeline parameter, which indicates that update operation doesn't support ingest pipeline, but if there's a default ingest pipeline or final ingest pipeline in the index, then that ingest pipeline can be executed sometimes, we need to document the usage clearly, do not confuse users.

Version: List the OpenSearch version to which this issue applies, e.g. 2.14, 2.12--2.14, or all.

2.19.0

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

opensearch-project/OpenSearch#16663

opensearch-project/OpenSearch#16712

@gaobinlong
Copy link
Contributor Author

Please assign this to me, thanks!

@Naarcha-AWS Naarcha-AWS added 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. and removed untriaged labels Dec 3, 2024
@Naarcha-AWS
Copy link
Collaborator

@gaobinlong: Feel free to ping me once you have a PR open for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Backlog - DEV Developer assigned to issue is responsible for creating PR.
Projects
None yet
Development

No branches or pull requests

2 participants