Shalin Shekhar Mangar schrieb:
On Tue, Jun 9, 2009 at 7:25 PM, Michael Ludwig <m...@as-guides.com>
wrote:
A filter query should probably be orthogonal to the primary query,
which means in plain English: unrelated to the primary query. To give
an example, I have a field "category", which is a required field. In
the class of searches where I use a filter on that field, the primary
search is for something entirely different, so in most cases, it will
not, or not necessarily, bias the primary result to any particular
distribution of the category values. I then allow the application to
apply filtering by category, incidentally, using faceting, which is a
typical usage pattern, I guess.
Yes and no. There are use-cases where the query is applicable only to
the filtered set. For example, when the same index contains many
different "types" of documents. It is just that the intersection may
need to do more or less work.
Sorry, I don't understand. I used to think that the engine applies the
filter to the primary query result. What you're saying here sounds as if
it could also pre-filter my document collection to then apply a query to
it (which should yield the same result). What does it mean that "the
query is applicable only to the filtered set"?
And thanks for having clarified the other points!
Michael Ludwig
