Document the usage of update document API with ingest pipeline #8874
Conversation
Signed-off-by: gaobinlong <[email protected]>
gaobinlong
requested review from
kolchfa-aws,
Naarcha-AWS,
vagimeli,
AMoo-Miki,
natebower,
dlvenable and
epugh
as code owners
|
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
|
@Naarcha-AWS please help to review this PR, thanks! |
There was a problem hiding this comment.
Thank you, @gaobinlong! Not sure what's meant by "final" ingest pipeline but I don't think we have to distinguish between those because the behavior is the same for both. Please see my suggestion and let me know if it conveys what we want to convey accurately. Thanks!
Co-authored-by: kolchfa-aws <[email protected]> Signed-off-by: gaobinlong <[email protected]>
kolchfa-aws
added
release-notes
Description
Document the usage of update document API with ingest pipeline clearly.
Issues Resolved
#8791
Version
2.19.0
Frontend features
If you're submitting documentation for an OpenSearch Dashboards feature, add a video that shows how a user will interact with the UI step by step. A voiceover is optional.
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.