-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[QUESTION] Consider reverting RefreshPolicy to HLRC #52
Comments
tlfeng
added
question
Questions about how things work, requests for help
:sanitize
Removing elastic specific artifacts
>FORK
Related to the fork process
labels
Feb 5, 2021
tlfeng
changed the title
Considering reverting RefreshPolicy to High-Level-Rest-Client
[QUESTION] Considering reverting RefreshPolicy to HLRC
Feb 5, 2021
tlfeng
changed the title
[QUESTION] Considering reverting RefreshPolicy to HLRC
[QUESTION] Consider reverting RefreshPolicy to HLRC
Feb 5, 2021
This was referenced Feb 5, 2021
tlfeng
referenced
this issue
Feb 7, 2021
This commit removes all trace of the security high level rest client and other reference to x-pack security Co-authored-by: Rabi Panda <[email protected]>
Inspired by @harold-wang in above commit ^, I checked the usage of "refresh" parameter. "refresh" parameter is widely used in REST APIs, and "Java High Level REST Client APIs": Get Source, ReIndex, Delete By Query, Update By Query I suggest we revert the commit elastic/elasticsearch@f063587, and bring the codes related to "RefreshPolicy" back. |
Resolved by above PR (# 55) |
ritty27
pushed a commit
to ritty27/OpenSearch
that referenced
this issue
May 12, 2024
…ensearch-project#52) (opensearch-project#53) Co-authored-by: István Zoltán Szabó <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
All the usage of
withRefresh()
has been removed in the commit 4d4f198 (remove all trace of x-pack security), and the code used for parsing therefresh
parameter in High Level Rest Client. Probably we could bring it back.Reason
Also written in my comment 4d4f198#r46835616.
"refresh" parameter is used in Get and Get Source API, etc.
The related code
RefreshPolicy
exists outside "x-pack" folder. Although Elasticsearch added a client side version of enumRefreshPolicy
in Hight-Level-Rest-Client under x-pack "security" package (by commit elastic/elasticsearch@f063587 ), it is nearly a copy of the original server side enumWriteRequest.RefreshPolicy
. The server sideRefreshPolicy
still valid.Affected test:
RequestConvertersTests
in PR [TEST] fix RequestConvertersTests failure #42The text was updated successfully, but these errors were encountered: