{"push_id":1062136877,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"226644ea2c44da61a70e5f3410936549424479c4","before":"013acf9179ad396a72b3062c9b3f965e4e248cf7","commits":[{"sha":"226644ea2c44da61a70e5f3410936549424479c4","author":{"email":"0b35fd4729a521ced70d3ea05bf74d1eb85c5108@gmail.com","name":"Adrien Grand"},"message":"Do not assume term queries use the inverted index. #17532\n\nWe have a couple places in the code base that assume that search is always done\non the inverted index. However with the new points API in Lucene 6, this is not\ntrue anymore. This commit makes MappedFieldType.indexedValueForSearch protected\nand fixes call sites to keep working for field types that use the inverted\nindex and either work differently ar throw an exception otherwise. For instance,\nit will still be possible to run cross_fields multi match queries on numeric\nfields, but the score contributions will not be blended as well as before, and\nsignificant terms aggregations on long terms will not be possible anymore since\npoints do not record document frequencies.","distinct":true,"url":"https://api.github.com/repos/NSIT/elasticsearch/commits/226644ea2c44da61a70e5f3410936549424479c4"}]}