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

Feature request - provide refresh and wait for active shards as configurables #28

Open
danizen opened this issue Mar 30, 2018 · 0 comments

Comments

@danizen
Copy link

danizen commented Mar 30, 2018

This is a simple one to implement, but low priority. Some customers may want to manipulate the refresh and wait_for_active_shards parameters when committing data to ealsticsearch.

That would mean providing something else than Collections.emptyMap() here:

This is related to my elasticsearch commit hang that caused my stop/resume strategy to fail, but isn't the cause of it. Just wanted to write down the need to configure these for some customers.

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

2 participants