Adrien Grand 226644ea2c Do not assume term queries use the inverted index. #17532 ... We have a couple places in the code base that assume that search is always done on the inverted index. However with the new points API in Lucene 6, this is not true anymore. This commit makes MappedFieldType.indexedValueForSearch protected and fixes call sites to keep working for field types that use the inverted index and either work differently ar throw an exception otherwise. For instance, it will still be possible to run cross_fields multi match queries on numeric fields, but the score contributions will not be blended as well as before, and significant terms aggregations on long terms will not be possible anymore since points do not record document frequencies.		2016-04-12 09:47:20 +02:00
..
fixtures	in the plugin: guard against HADOOP_HOME in environment on any platform.	2015-12-21 02:21:53 -05:00
framework	Do not assume term queries use the inverted index. #17532	2016-04-12 09:47:20 +02:00
logger-usage	Remove System.out.println and Throwable.printStackTrace from tests	2016-03-15 15:40:37 +01:00
build.gradle	Revert "Build: Switch to maven-publish plugin"	2016-03-18 17:22:25 -07:00