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] Documentation of batch ingestion feature #7305

Closed
2 of 4 tasks
chishui opened this issue Jun 6, 2024 · 8 comments · Fixed by #7408
Closed
2 of 4 tasks

[DOC] Documentation of batch ingestion feature #7305

chishui opened this issue Jun 6, 2024 · 8 comments · Fixed by #7408
Assignees
Labels
1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. v2.15.0

Comments

@chishui
Copy link
Contributor

chishui commented Jun 6, 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.
We added this batch ingestion feature, user can now use it to accelerate their ingestion time if the ingest pipeline has ML processors text_embedding and sparse_encoding which connects to external ML servers.

The documentation changes would include a new parameter in _bulk API, a new paragraph in ingest processor to explain the batch enabled processors, and a new page to introduce this feature.

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

@hdhalter
Copy link
Contributor

hdhalter commented Jun 6, 2024

Thanks, @chishui! Is this being released in 2.15?

@chishui
Copy link
Contributor Author

chishui commented Jun 7, 2024

Thanks, @chishui! Is this being released in 2.15?

Yes, sorry that I forgot to mention the version

@hdhalter
Copy link
Contributor

Hi @chishui , what is the ETA for this doc PR? The first release candidate is today. Thanks!

@peterzhuamazon
Copy link
Member

Hi @chishui could you please provide a PR for this since it is labeled for 2.15 and we are approaching the release date?

Thanks.

@chishui
Copy link
Contributor Author

chishui commented Jun 14, 2024

Since there has been an active discussion on deprecating the parameter we introduced (opensearch-project/OpenSearch#14283), whether we should announce the feature is still pending decision.

@peterzhuamazon
Copy link
Member

Hi @chishui please give a decision on this next Monday/Tuesday.
As we need to stay on the timeline.

If you have concerns including in 2.15.0 I would suggest removing the 2.15.0 label until resurface. That way, this would not be a blocker for 2.15.0 anymore.

Thanks.

@hdhalter hdhalter removed the v2.15.0 label Jun 14, 2024
@hdhalter
Copy link
Contributor

Hi @chishui, I removed the 2.15 label. If something changes, we'll be happy to help get the content updated.

@chishui
Copy link
Contributor Author

chishui commented Jun 19, 2024

PR is raised, can we add the 2.15 label back? Thanks

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. v2.15.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants