-
Notifications
You must be signed in to change notification settings - Fork 66
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
Completed ISM specs and tests. #578
Conversation
Spec Test Coverage Analysis
|
Changes AnalysisCommit SHA: f746a39 API ChangesSummary
ReportThe full API changes report is available at: https://github.com/opensearch-project/opensearch-api-specification/actions/runs/10904509514/artifacts/1942889501 API Coverage
|
5c5fb2e
to
5fcbc26
Compare
spec/namespaces/ism.yaml
Outdated
/_plugins/_ism/add: | ||
post: | ||
operationId: ism.add.0 | ||
x-operation-group: ism.add |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be in the same group as ism.add_policy
similar to {index}/_search
and /_search
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as for change_policy
they have different parameters, one specifies the index in the query, the other in the path.
spec/namespaces/ism.yaml
Outdated
/_plugins/_ism/remove: | ||
post: | ||
operationId: ism.remove.0 | ||
x-operation-group: ism.remove |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be in the same group as ism.remove_policy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as for change_policy
they have different parameters, one specifies the index in the query, the other in the path.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's correct. But as far as the clients users are concerned, which is what the operation group is for, where the index
param is put in the URL request is irrelevant. We have many API actions, like search, that also allows the index to be specified as either a path param or a query param, the generated clients will favor use it as a path param regardless. In a generated client, client.ism.remove
and client.ism_remove_policy
will pretty much be identical to each other and it will lead to confusion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I had to add query
to the one that doesn't really take it, but it won't matter from the client POV I think.
spec/namespaces/ism.yaml
Outdated
/_plugins/_ism/change_policy: | ||
post: | ||
operationId: ism.change.0 | ||
x-operation-group: ism.change |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be in the same group as ism.change_policy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But they have different parameters, one specifies the index in the query, the other in the path. So if you try to make them the same group you get this:
{
file: 'namespaces/ism.yaml',
location: 'Operation Group: ism.change_policy',
message: "2 'ism.change_policy' operations must have an identical set of query parameters."
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty sure you can still have index
as a query string in the one that already accepts index
in path, and the query string param will be ignored just like other API actions that allow this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
Added HEAD /_plugins/_ism/policies/{policy_id}. Added GET /_plugins/_ism/explain. Added /_plugins/refresh_search_analyzers. Added /_plugins/_ism/retry/{index}. Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Signed-off-by: dblock <dblock@amazon.com>
Description
Completed ISM specs and tests.
Issues Resolved
Closes #224.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.