Currently percolator allows you to control the number of matches with a size parameter. However, it always reports the total number of matches and thus is forced to evaluate all queries irrespective of the size. On larger percolator deployments, the total number of matches is sometimes not required and only the
Request the addition of a total_hits parameter. If true, all queries will be evaluated. If false, all queries will be evaluated only if no size parameter is provided - otherwise Percolator will simply drop out.
Introduces considerations with sorting that need discussion
Currently percolator allows you to control the number of matches with a size parameter. However, it always reports the total number of matches and thus is forced to evaluate all queries irrespective of the size. On larger percolator deployments, the total number of matches is sometimes not required and only the
Request the addition of a total_hits parameter. If true, all queries will be evaluated. If false, all queries will be evaluated only if no size parameter is provided - otherwise Percolator will simply drop out.
Introduces considerations with sorting that need discussion