Skip to content

Commit

Permalink
[DOC] Clarify outcome of index operation
Browse files Browse the repository at this point in the history
Fix elastic#222

(cherry picked from commit c47f7e50f6b4fcd7af07efedff0e080366d98deb)
  • Loading branch information
costin committed Aug 1, 2014
1 parent c5dc79a commit 41a520a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/src/reference/asciidoc/core/configuration.adoc
Expand Up @@ -121,7 +121,7 @@ integration for more details about using JSON directly.

`es.write.operation` (default index)::
The write operation {eh} should peform - can be any of:
`index` (default);; new data is added while existing data (based on its id) is updated.
`index` (default);; new data is added while existing data (based on its id) is replaced (reindexed).
`create`;; adds new data - if the data already exists (based on its id), an exception is thrown.
`update`;; updates existing data (based on its id). If no data is found, an exception is thrown.
`upsert`;; known as _merge_ or insert if the data does not exist, updates if the data exists (based on its id).
Expand Down

0 comments on commit 41a520a

Please sign in to comment.