honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update refresh.asciidoc 

Fix grammar and example
This commit is contained in:
Christoph Wurm 2016-07-05 13:49:25 +02:00 committed by GitHub
parent d1727653dd
commit 768beea6c7
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/reference/docs/refresh.asciidoc
View File

@ -17,7 +17,7 @@ indexing and a search standpoint.
Wait for the changes made by the request to be made visible by a refresh before Wait for the changes made by the request to be made visible by a refresh before
replying. This doesn't force an immediate refresh, rather, it waits for a replying. This doesn't force an immediate refresh, rather, it waits for a
refresh happen. Elasticsearch automatically refreshes shards that have changed refresh to happen. Elasticsearch automatically refreshes shards that have changed
every `index.refresh_interval` which defaults to one second. That setting is every `index.refresh_interval` which defaults to one second. That setting is
<<dynamic-index-settings,dynamic>>. The <<indices-refresh>> API will also <<dynamic-index-settings,dynamic>>. The <<indices-refresh>> API will also
cause the request to return, as will setting `refresh` to `true` on any of the cause the request to return, as will setting `refresh` to `true` on any of the
@ -36,7 +36,7 @@ use `refresh=false`, or, because that is the default, just leave the `refresh`
parameter out of the URL. That is the simplest and fastest choice. parameter out of the URL. That is the simplest and fastest choice.
If you absolutely must have the changes made by a request visible synchronously If you absolutely must have the changes made by a request visible synchronously
with the request then you must get to pick between putting more load on with the request then you must pick between putting more load on
Elasticsearch (`true`) and waiting longer for the response (`wait_for`). Here Elasticsearch (`true`) and waiting longer for the response (`wait_for`). Here
are a few points that should inform that decision: are a few points that should inform that decision:
@ -97,7 +97,7 @@ search:
-------------------------------------------------- --------------------------------------------------
PUT /test/test/3 PUT /test/test/3
{"test": "test"} {"test": "test"}
PUT /test/test/4?refresh=true PUT /test/test/4?refresh=false
{"test": "test"} {"test": "test"}
-------------------------------------------------- --------------------------------------------------
// CONSOLE // CONSOLE