[
https://issues.apache.org/jira/browse/SOLR-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616349#action_12616349
]
Hoss Man commented on SOLR-650:
-------------------------------
-1
this idea has been discussed before, and i'm still opposed to it...
http://www.nabble.com/new-user%3A-some-questions-about-parameters-and-query-syntax-to17514279.html#a17572002
http://www.nabble.com/Re%3A--jira--Commented%3A-%28SOLR-247%29-Allow-facet.field%3D*-to-facet-on-all-fields-%28without-knowing-what-they-are%29-p10771433.html
...among other things it breaks backwards compatibility for people who
currently use facet.field on field names that contain whitespace. If being
consistent were worth breaking back compatibility then I would rather see us
remove the "split" call for all params where it is currently used, then to add
splitting to any existing params.
The only way i'm going to be on board with something like this is if it's a
customization via some sort of general field name aliasing/globing
configuration mechanism...
http://wiki.apache.org/solr/FieldAliasesAndGlobsInParams
> facet.field should accept field names separated by spaces or commas
> -------------------------------------------------------------------
>
> Key: SOLR-650
> URL: https://issues.apache.org/jira/browse/SOLR-650
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Lars Kotthoff
> Priority: Minor
> Attachments: SOLR-650.patch
>
>
> The current version of SimpleFacets does not support specifying several
> fields to facet on in a single facet.field parameter; it has to be specified
> for each field. This behaviour is inconcistent with the other parameters
> which accept field names as arguments -- they allow specifying multiple field
> names either as a comma- or space-separated list or by specifying the
> parameter multiple times.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
