I'm doing phrase_prefix search for 'engineer' and I get 36 count for term
'Engineering' in 'skills' field facet. Next I apply a term filter on that
field for 'Engineering' and in the new filtered results now the count for
'Engineering' in the facet is 42.
The filtered query returns 42 results, and each document does match the
facet, that is, they all contain 'Engineering' as a skill.
So I would expect the non-filtered query to have a 42 count for the
'Engineering' term in 'skills' facet, but as I mentioned above it's just 36.
just to make sure I understood your query correctly:
Your phrase prefix search does not search in the skills field? This means
the search for engineer goes somewhere else.
Second, when you add the term filter, do you keep the query or are you
simply replacing it? Not sure I got that right.
Can you possibly create a gist using your real data and including all the
curl calls you used, so one can recreate it locally and see what happens?
--Alex
On Fri, Jan 10, 2014 at 4:21 PM, Santiago Gaviria sgaviria@gmail.comwrote:
I'm doing phrase_prefix search for 'engineer' and I get 36 count for term
'Engineering' in 'skills' field facet. Next I apply a term filter on that
field for 'Engineering' and in the new filtered results now the count for
'Engineering' in the facet is 42.
The filtered query returns 42 results, and each document does match the
facet, that is, they all contain 'Engineering' as a skill.
So I would expect the non-filtered query to have a 42 count for the
'Engineering' term in 'skills' facet, but as I mentioned above it's just 36.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.