-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Simplify underscore requirements in parameters #26886
Comments
Discussed in FixItFriday. We agree that we should make this consistent with where these parameters are used in other APIs, eg:
This should be deprecated for as long as possible before making the breaking change. |
Hello, |
Yes. We make it consistent with how these parameters are used elsewhere (obviously with a deprecation period).
thanks for pointing those out. we should do the same in these APIs |
I would like to work on this if no one is working. |
I'm looking into this as well |
@sumanthrao @orinn248 I have already finished the implementation on this, will create a PR soon |
Thanks @mayya-sharipova, I’m removing the adoptme label. |
Stardardize underscore requirements in parameters across different type of requests: _index, _type, _source, _id keep their underscores params like version and retry_on_conflict will be without underscores BulkRequest, MultiGetRequest, TermVectorcRequest, MoreLikeThisQuery were changed Closes elastic#26886
Stardardize underscore requirements in parameters across different type of requests: _index, _type, _source, _id keep their underscores params like version and retry_on_conflict will be without underscores BulkRequest, MultiGetRequest, TermVectorcRequest, MoreLikeThisQuery were changed Closes elastic#26886
Stardardize underscore requirements in parameters across different type of requests: _index, _type, _source, _id keep their underscores params like version and retry_on_conflict will be without underscores In 6.x these parameters are deprecated and produce deprecated warnings. BulkRequest, MultiGetRequest, TermVectorcRequest, MoreLikeThisQuery were changed Closes elastic#26886
Stardardize underscore requirements in parameters across different type of requests: _index, _type, _source, _id keep their underscores params like version and retry_on_conflict will be without underscores Throw an error if older versions of parameters are used BulkRequest, MultiGetRequest, TermVectorcRequest, MoreLikeThisQuery were changed Closes elastic#26886
…pe of requests: _index, _type, _source, _id keep their underscores params like version and retry_on_conflict will be without underscores Throw an error if older versions of parameters are used BulkRequest, MultiGetRequest, TermVectorcRequest, MoreLikeThisQuery were changed Related to elastic#27040 Closes elastic#26886
Stardardize underscore requirements in parameters across different type of requests: _index, _type, _source, _id keep their underscores params like version and retry_on_conflict will be without underscores Throw an error if older versions of parameters are used BulkRequest, MultiGetRequest, TermVectorcRequest, MoreLikeThisQuery were changed Closes #26886
Stardardize underscore requirements in parameters across different type of requests: _index, _type, _source, _id keep their underscores params like version and retry_on_conflict will be without underscores Log a warning if older versions of these parameters are used BulkRequest, MultiGetRequest, TermVectorcRequest, MoreLikeThisQuery were changed Closes #26886
Describe the feature: When updating a document through the update API, we have to specify parameters like retry_on_conflict without a leading _ in query-string parameters, but on the bulk API, we have to include the parameter as _retry_on_conflict in the action/meta line. Remembering when to use _ can be confusing to the user. This is even more true when using a library like elasticsearch.js where you have to specify parameters such as index, type, and id in one case and _index, _type, _id in another. Elasticsearch should accept parameters in the action/meta line with or without the leading _, and it seems this is already true of some parameters like version/_version and routing/_routing.
The text was updated successfully, but these errors were encountered: