lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jae Joo <jaejo...@gmail.com>
Subject Re: facet.method=smart
Date Fri, 04 Dec 2020 18:19:36 GMT
Thanks!

Jae

On Fri, Dec 4, 2020 at 1:38 AM Radu Gheorghe <radu.gheorghe@sematext.com>
wrote:

> Hi Jae,
>
> No, it’s not smarter than explicitly defining, for example enum for a
> low-cardinality field.
>
> Think of “smart” as a default path, and explicit definitions as some
> “hints”. You can see that default path in this function:
> https://github.com/apache/lucene-solr/blob/master/solr/core/src/java/org/apache/solr/search/facet/FacetField.java#L74
>
> Note that I’ve added a PR with a bit more explanations for the “hits”
> here: https://github.com/apache/lucene-solr/pull/2057 But if you’re
> missing some info, please feel free to comment (here or there), I could add
> some more info.
>
> Best regards,
> Radu
> --
> Sematext Cloud - Full Stack Observability - https://sematext.com
> Solr and Elasticsearch Consulting, Training and Production Support
>
> > On 30 Nov 2020, at 22:46, Jae Joo <jaejoo18@gmail.com> wrote:
> >
> > Is "smart" really smarter than one explicitly defined?
> >
> > For "emun" type, would it be faster to define facet.method=enum than
> smart?
> >
> > Jae
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message