lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-2251) use facet "key" as override for field name when looking for per field facet options
Date Wed, 24 Nov 2010 12:42:14 GMT

    [ https://issues.apache.org/jira/browse/SOLR-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935308#action_12935308
] 

Tim commented on SOLR-2251:
---------------------------

Yup, I wasn't sure about the original intended behavior but the enhancement seemed to make
sense to me.  Thanks for considering it.

> use facet "key" as override for field name when looking for per field facet options
> -----------------------------------------------------------------------------------
>
>                 Key: SOLR-2251
>                 URL: https://issues.apache.org/jira/browse/SOLR-2251
>             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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message