Docs: Display reindex/update by query API and fix build doc issue

The documentation existed, but was not linked anywhere.
Also fixed the docs to make sure they build with this enabled.
This commit is contained in:
Alexander Reelsen 2016-03-18 10:44:16 +01:00
parent b693a520ee
commit 2dffad9ec3
3 changed files with 10 additions and 11 deletions

View File

@ -29,10 +29,14 @@ include::docs/delete.asciidoc[]
include::docs/update.asciidoc[]
include::docs/update-by-query.asciidoc[]
include::docs/multi-get.asciidoc[]
include::docs/bulk.asciidoc[]
include::docs/reindex.asciidoc[]
include::docs/termvectors.asciidoc[]
include::docs/multi-termvectors.asciidoc[]

View File

@ -1,5 +1,5 @@
[[docs-reindex]]
==== Reindex API
== Reindex API
`_reindex`'s most basic form just copies documents from one index to another.
This will copy documents from `twitter` into `new_twitter`:
@ -420,9 +420,7 @@ will finish when their sum is equal to the `total` field.
[float]
=== Examples
==== Change the name of a field
=== Reindex to change the name of a field
`_reindex` can be used to build a copy of an index with renamed fields. Say you
create an index containing documents that look like this:

View File

@ -1,5 +1,5 @@
[[docs-update-by-query]]
==== Update By Query API
== Update By Query API
The simplest usage of `_update_by_query` just performs an update on every
document in the index without changing the source. This is useful to
@ -101,8 +101,8 @@ Just as in {ref}/docs-update.html[Update API] you can set `ctx.op = "noop"` if
your script decides that it doesn't have to make any changes. That will cause
`_update_by_query` to omit that document from its updates. Setting `ctx.op` to
anything else is an error. If you want to delete by a query you can use the
<<plugins-delete-by-query,Delete by Query Plugin>> instead. Setting any other
field in `ctx` is an error.
{plugins}/delete-by-query.html[Delete by Query plugin] instead. Setting any
other field in `ctx` is an error.
Note that we stopped specifying `conflicts=proceed`. In this case we want a
version conflict to abort the process so we can handle the failure.
@ -267,11 +267,8 @@ progress by adding the `updated`, `created`, and `deleted` fields. The request
will finish when their sum is equal to the `total` field.
[float]
=== Examples
[[picking-up-a-new-property]]
==== Pick up a new property
=== Pick up a new property
Say you created an index without dynamic mapping, filled it with data, and then
added a mapping value to pick up more fields from the data: