Igor Motov 90da268237 Remove support for boost in copy_to field ... Currently, boosting on `copy_to` is misleading and does not work as originally specified in #4520. Instead of boosting just the terms from the origin field, it boosts the whole destination field. If two fields copy_to a third field, one with a boost of 2 and another with a boost of 3, all the terms in the third field end up with a boost of 6. This was not the intention. The alternative: to store the boost in a payload for every term, results in poor performance and inflexibility. Instead, users should either (1) query the common field AND the field that requires boosting, or (2) the multi_match query will soon be able to perform term-centric cross-field matching that will allow per-field boosting at query time (coming in 1.1).		2014-01-31 14:34:01 -05:00
..
fields	Deprecate document _boost	2014-01-09 16:04:01 +01:00
types	Remove support for boost in copy_to field	2014-01-31 14:34:01 -05:00
conf-mappings.asciidoc	Migrated documentation into the main repo	2013-08-29 01:24:34 +02:00
date-format.asciidoc	rename and document "index.mapping.date.parse_upper_inclusive" setting for date fields	2013-10-28 15:48:31 +01:00
dynamic-mapping.asciidoc	[DOCS] Changed all store:yes/no to store:true/false	2013-11-07 16:57:18 +01:00
fields.asciidoc	Migrated documentation into the main repo	2013-08-29 01:24:34 +02:00
meta.asciidoc	Migrated documentation into the main repo	2013-08-29 01:24:34 +02:00
types.asciidoc	Replaced the multi-field type in favour for the multi fields option that can be set on any core field.	2014-01-13 09:21:53 +01:00