Skip to content
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

Manage concurrent updates #44

Closed
To-om opened this issue Jan 22, 2018 · 0 comments
Closed

Manage concurrent updates #44

To-om opened this issue Jan 22, 2018 · 0 comments
Assignees
Milestone

Comments

@To-om
Copy link
Contributor

To-om commented Jan 22, 2018

The aim of this issue is to give to application more control on ElasticSearch behavior when concurrent accesses occur on the same document.
In update methods, a new parameter is added to define:

  • if ES must retry the update if conflict occurs,
  • the refresh policy
  • the document version targeted by the update
@To-om To-om added this to the 1.5.0 milestone Jan 22, 2018
@To-om To-om self-assigned this Jan 22, 2018
@To-om To-om closed this as completed Jan 23, 2018
@To-om To-om modified the milestones: 1.5.0, 1.4.3 Jan 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant