Martijn van Groningen ff5527f037 percolator: Forbid the usage or `range` queries with a range based on the current time ... If there are percolator queries containing `range` queries with ranges based on the current time then this can lead to incorrect results if the `percolate` query gets cached. These ranges are changing each time the `percolate` query gets executed and if this query gets cached then the results will be based on how the range was at the time when the `percolate` query got cached. The ExtractQueryTermsService has been renamed `QueryAnalyzer` and now only deals with analyzing the query (extracting terms and deciding if the entire query is a verified match) . The `PercolatorFieldMapper` is responsible for adding the right fields based on the analysis the `QueryAnalyzer` has performed, because this is highly dependent on the field mappings. Also the `PercolatorFieldMapper` is responsible for creating the percolate query.		2016-07-08 14:20:56 +02:00
..
src	percolator: Forbid the usage or `range` queries with a range based on the current time	2016-07-08 14:20:56 +02:00
build.gradle	Moved the percolator from core to its own module	2016-05-24 11:01:57 +02:00