11 Commits

Author SHA1 Message Date
Patrick Peschlow
340e0efcaa Docs: cross_type query needs to be cross_fields
Closes #8021
2014-10-15 18:27:48 +02:00
Clinton Gormley
cb00d4a542 Docs: Removed all the added/deprecated tags from 1.x 2014-09-26 21:04:42 +02:00
Clinton Gormley
cf001d6837 Docs: Adds missing explanation to multi-match
Closes #7281
2014-09-07 11:30:52 +02:00
jnguyenx
1883f74cc0 Docs: Fixed missing comma in multi match query example 2014-07-03 08:17:09 +02:00
violuke
4f99f0c6f1 [DOCS] Improved readability of multi-match query docs 2014-06-03 14:23:34 +02:00
violuke
0020e5fc0a [DOCS] Improved grammar in multi-match query docs 2014-06-03 11:50:41 +02:00
Clinton Gormley
65906d176a Update multi-match-query.asciidoc
Typo
2014-04-16 15:41:38 +02:00
bleskes
5d832374dd Update Documentation Feature Flags [1.1.0] 2014-03-25 17:51:30 +01:00
Simon Willnauer
90e57c15e8 [DOCS]: fixed small problem in example json 2014-02-26 16:40:04 +01:00
Simon Willnauer
162ca99376 Added cross_fields mode to multi_match query
`cross_fields` attemps to treat fields with the same analysis
configuration as a single field and uses maximum score promotion or
combination of the scores based depending on the `use_dis_max` setting.
By default scores are combined. `cross_fields` can also search across
fields of hetrogenous types for instance if numbers can be part of
the query it makes sense to search also on numeric fields if an analyzer
is provided in the reqeust.

Relates to #2959
2014-02-06 17:15:55 +01:00
Clinton Gormley
822043347e Migrated documentation into the main repo 2013-08-29 01:24:34 +02:00