You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Tim (JIRA)" <ji...@apache.org> on 2010/11/23 13:57:13 UTC
[jira] Created: (SOLR-2251) Facet "key" not used when setting
mincount, etc on individual facets
Facet "key" not used when setting mincount, etc on individual facets
--------------------------------------------------------------------
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
[jira] Commented: (SOLR-2251) use facet "key" as override for field
name when looking for per field facet options
Posted by "Tim (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (SOLR-2251) use facet "key" as override for field
name when looking for per field facet options
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Updated: (SOLR-2251) use facet "key" as override for field
name when looking for per field facet options
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-2251:
---------------------------
Summary: use facet "key" as override for field name when looking for per field facet options (was: Facet "key" not used when setting mincount, etc on individual facets)
> 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
[jira] Commented: (SOLR-2251) Facet "key" not used when setting
mincount, etc on individual facets
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935123#action_12935123 ]
Hoss Man commented on SOLR-2251:
--------------------------------
just to clarify: the "key" local param was original added to support multiselect faceting with alternate exclusions -- that's why the only documentation about it is in the [Multi-Select faceting docs|http://wiki.apache.org/solr/SimpleFacetParameters#key_:_Changing_the_output_key] and nothing in those docs suggest that specifying a key will cause it to use that key when looking or param names.
that said: i agree that i would be good if facet params work the way you describe
if a user specifies {{facet.field={!key=alt_name}orig_name}} then the order of precedence for options like facet.mincount should be...
* f.alt_name.facet.mincount
* f.orig_name.facet.mincount
* facet.mincount
...ditto for facet.query, facet.range, and facet.date.
> Facet "key" not used when setting mincount, etc on individual facets
> --------------------------------------------------------------------
>
> 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