-
Notifications
You must be signed in to change notification settings - Fork 502
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 cat/pit_segments API #7614
Labels
Comments
dblock
changed the title
[DOC] Point-in-time Clarification please.
[DOC] Document cat/pit_segments API
Jul 2, 2024
There's some confusion I think. I raised a question in Slack on the API, but it was the
This will return nothing because there are no segments (no data), which deserves to be noted.
Insert data
Now it returns something.
This API also supports getting PIT segments for a specific PIT. With 2 PITs.
It's a GET with a body, yes.
|
Naarcha-AWS
added
the
1 - Backlog - DOC
Doc writer assigned to issue responsible for creating PR.
label
Jul 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What do you want to do?
Tell us about your request. Provide a summary of the request.
Related to: opensearch-project/opensearch-api-specification#373
We should probably mention that if the index for which you are creating a PIT doesn't have any data in it, that the call to list the pit_segments either by ID or with _all will return an empty response with a response code of 400.
*Version: List the OpenSearch version to which this issue applies, e.g. 2.14, 2.12--2.14, or all.
2.14
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
https://opensearch.slack.com/archives/C04UM4D6XN2/p1719956200725049?thread_ts=1719946620.686809&cid=C04UM4D6XN2
The text was updated successfully, but these errors were encountered: