lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Resolved: (SOLR-2251) use facet "key" as override for field name when looking for per field facet options
Date Wed, 16 Mar 2011 21:18:29 GMT


Hoss Man resolved SOLR-2251.

    Resolution: Duplicate

I just realized this is actually a dup of SOLR-1351

> use facet "key" as override for field name when looking for per field facet options
> -----------------------------------------------------------------------------------
>                 Key: SOLR-2251
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 1.4.1
>            Reporter: Tim
>            Priority: Minor
> The "key" parameter that is used for aliasing output is very helpful in simplifying the
readability of complex facets.  However it doesn't seem that this same alias can be used when
configuring facets of individual fields.  The following example that does not use the key
parameter works fine under 1.4.1:
> rows=0&q=*:*+NOT+customers.blocked:1&facet=true&f.customers_name.facet.mincount=2&facet.field=customers_name
> <lst name="customers_name">
>   <int name="jone">2</int>
> </lst>
> The example below also works and does use the key parameter, however note that we're
still using the original field name when referring to f.customers_name.facet.mincount:
> rows=0&q=*:*+NOT+customers.blocked:1&facet=true&f.customers_name.facet.mincount=2&facet.field={!key=alt_name}customers_name
> <lst name="customers_name">
>   <int name="jone">2</int>
> </lst>
> The final example below does not work.  It uses the alias established by the key parameter
to configure the mincount setting for the customers_name field.
> rows=0&q=*:*+NOT+customers.blocked:1&facet=true&f.alt_name.facet.mincount=2&facet.field={!key=alt_name}customers_name
> <lst name="alt_name">
>   <int name="jone">2</int>
>   <int name="tim">1</int>
>   <int name="sami">0</int>
> </lst>
> This is a trivial example.  The behavior becomes much more important when talking about
facet queries.

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message