I'm confused here. What do you mean by "facet filtering"? Your
examples have no facets at all, just a _filter query_.

I'll assume you want to use filter query (fq), and faceting has
nothing to do with it. This is one of the tricky bits of docValues.
While it's _possible_ to search on a field that's defined as above,
it's very inefficient since there's no "inverted index" for the field,
you specified 'indexed="false" '. So the docValues are searched, and
it's essentially a table scan.

If you mean to search against this field, set indexed="true". You'll
have to completely reindex your corpus of course.

If you intend to facet, group or sort on this field, you should _also_
have docValues="true".


On Mon, Feb 19, 2018 at 7:47 AM, MOUSSA MZE Oussama-ext
<oussama.moussa-mze-...@pole-emploi.fr> wrote:
> Hi
> We have following environement :
> 3 nodes cluster
> 1 shard
> Replication factor = 2
> 8GB per node
> 29 millions of documents
> We've faceting over field "motifPresence" defined as follow:
> <field name="motifPresence" type="string" docValues="true" indexed="false" 
> stored="true" required="false"/>
> Once the user selects motifPresence filter we executes search again with:
> fq: (value1 OR value2 OR value3 OR ...)
> The problem is: During facet filtering query is too slow and her response 
> time is greater than main search (without facet filtering).
> Thanks in advance!

Reply via email to