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

Document that _index is a virtual field and only supports term queries 

Closes #15070
Closes #15081
This commit is contained in:
Clinton Gormley 2015-11-30 08:42:56 +01:00
parent 1685126bb6
commit 72be42d742
1 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/reference/mapping/fields/index-field.asciidoc
View File

@ -1,10 +1,17 @@
[[mapping-index-field]] [[mapping-index-field]]
=== `_index` field === `_index` field
When performing queries across multiple indexes, it is sometimes desirable When performing queries across multiple indexes, it is sometimes desirable to
to add query clauses that are associated with documents of only certain add query clauses that are associated with documents of only certain indexes.
indexes. The `_index` field allows matching on the index a document was The `_index` field allows matching on the index a document was indexed into.
indexed into. Its value is accessible in queries, aggregations, scripts, and when sorting: Its value is accessible in `term`, or `terms` queries, aggregations,
scripts, and when sorting:
NOTE: The `_index` is exposed as a virtual field -- it is not added to the
Lucene index as a real field. This means that you can use the `_index` field
in a `term` or `terms` query (or any query that is rewritten to a `term`
query, such as the `match`, `query_string` or `simple_query_string` query),
but it does not support `prefix`, `wildcard`, `regexp`, or `fuzzy` queries.
[source,js] [source,js]
-------------------------- --------------------------