From 295398565977e2cef83baf24b4b5a000316360bb Mon Sep 17 00:00:00 2001 From: Nik Everett Date: Mon, 24 Aug 2015 12:19:07 -0400 Subject: [PATCH] [docs] Document noop behavior of index api Relates to #12969 --- docs/reference/docs/index_.asciidoc | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/docs/reference/docs/index_.asciidoc b/docs/reference/docs/index_.asciidoc index 134bdeb88f2..cd239922de2 100644 --- a/docs/reference/docs/index_.asciidoc +++ b/docs/reference/docs/index_.asciidoc @@ -353,7 +353,23 @@ occurs, so that the document appears in search results immediately, the `refresh` parameter can be set to `true`. Setting this option to `true` should *ONLY* be done after careful thought and verification that it does not lead to poor performance, both from an indexing and a search standpoint. Note, getting -a document using the get API is completely realtime. +a document using the get API is completely realtime and doesn't require a +refresh. + +[float] +[[index-noop]] +=== Noop Updates + +When updating a document using the index api a new version of the document is +always created even if the document hasn't changed. If this isn't acceptable +use the `_update` api with `detect_noop` set to true. This option isn't +available on the index api because the index api doesn't fetch the old source +and isn't able to compare it against the new source. + +There isn't a hard and fast rule about when noop updates aren't acceptable. +It's a combination of lots of factors like how frequently your data source +sends updates that are actually noops and how many queries per second +elasticsearch runs on the shard with receiving the updates. [float] [[timeout]]