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

Jump to bottom

Flush API: remove refresh flag #3689

Closed
kimchy opened this issue Sep 13, 2013 · 0 comments
Closed

Flush API: remove refresh flag #3689

kimchy opened this issue Sep 13, 2013 · 0 comments
Labels
>breaking >enhancement v0.90.4 v1.0.0.Beta1

Comments

@kimchy
Copy link
Member

kimchy commented Sep 13, 2013

Refresh flag in flush is problematic, since the shards refresh is allowed to execute on is different compared to the flush shards. In order to do flush and then refresh, they should be executed as separate APIs when needed.
@kimchy kimchy closed this as completed in 7cc48c8 Sep 13, 2013
kimchy added a commit that referenced this issue Sep 13, 2013
@kimchy
Flush API: remove refresh flag
7bd8efd 
Refresh flag in flush is problematic, since the shards refresh is allowed to execute on is different compared to the flush shards. In order to do flush and then refresh, they should be executed as separate APIs when needed.
closes #3689
kimchy added a commit that referenced this issue Sep 13, 2013
@kimchy
Flush API: remove refresh flag
e947979 
Refresh flag in flush is problematic, since the shards refresh is allowed to execute on is different compared to the flush shards. In order to do flush and then refresh, they should be executed as separate APIs when needed.
closes #3689
@lukas-vlcek lukas-vlcek mentioned this issue Sep 18, 2013
Closed
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@kimchy
Flush API: remove refresh flag
07f65dd 
Refresh flag in flush is problematic, since the shards refresh is allowed to execute on is different compared to the flush shards. In order to do flush and then refresh, they should be executed as separate APIs when needed.
closes elastic#3689
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@kimchy
Flush API: remove refresh flag
52444cb 
Refresh flag in flush is problematic, since the shards refresh is allowed to execute on is different compared to the flush shards. In order to do flush and then refresh, they should be executed as separate APIs when needed.
closes elastic#3689
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>breaking >enhancement v0.90.4 v1.0.0.Beta1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy