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.

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

Add migration guide note for _flush?wait_if_ongoing #20603

Merged
merged 2 commits into from
Sep 21, 2016
Merged

Add migration guide note for _flush?wait_if_ongoing #20603

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
413f10e
Add migration guide note for `_flush?wait_if_ongoing`
s1monw Sep 21, 2016
f77e5d3
Move flush change to index-apis.asciidoc
s1monw Sep 21, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/reference/migration/migrate_5_0/index-apis.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,3 +69,10 @@ prefer there to be only one (obvious) way to do things like this.

As of 5.0 indexing a document with `op_type=create` without specifying an ID is not
supported anymore.

==== Flush API

The `wait_if_ongoing` flag default has changed to `true` causing `_flush` calls to wait and block
if another flush operation is currently running on the same shard. In turn, if `wait_if_ongoing` is set to
`false` and another flush operation is already running the flush is skipped and the shards flush call will return
immediately without any error. In previous versions `flush_not_allowed` exceptions where reported for each skipped shard.