Skip to content

Optimize API: Change flush and refresh to default to true and not false #187

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.

Sign up for GitHub

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
Closed
kimchy opened this issue May 21, 2010 · 1 comment
Closed

Optimize API: Change flush and refresh to default to true and not false #187

kimchy opened this issue May 21, 2010 · 1 comment
Labels
>enhancement v0.08.0

Comments

@kimchy
Copy link
Member

kimchy commented May 21, 2010

Make more sense to do a flush and refresh after optimize by default then not.
@kimchy
Copy link
Member Author

kimchy commented May 21, 2010

Optimize API: Change flush and refresh to default to true and not false, closed by 6191bf9.

@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
rmuir added a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
@rmuir
Merge pull request elastic#187 from rmuir/tika_tests
ecc8912 
Add test documents from tika test suite
ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
@jakommo
Added default value to es_scripts_fileglob. Could fail if undefined.
8a7656c 
Closes elastic#187
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@dliappis
Require checking/rescheduling of nightly jobs during releases (elasti…
07d387e 
…c#187)

Also clarify schedule of nightlies and revision picking strategy.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>enhancement v0.08.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy