[
https://issues.apache.org/jira/browse/SOLR-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616354#action_12616354
]
Lars Kotthoff commented on SOLR-650:
------------------------------------
bq. ...among other things it breaks backwards compatibility for people who
currently use facet.field on field names that contain whitespace.
Do you think that this would be much of an issue? Using field names with
whitespace in them breaks almost everywhere else (retrieving fields,
highlighting...) -- I don't think that many people are using fields with
whitespace in them at all. Obviously I can only speculate about this though, so
do correct me if I'm wrong.
bq. 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...
I think making the way parameters like this are handled consistent is a first
step in that direction. It's going to be much easier to design and implement
general field configuration parameters when they are handled in a uniform way.
bq. Wouldn't your approach be inconsistent with the way multi-valued parameters
are handled in HTTP?
Sort of, but so is the rest of Solr.
bq. I'd say put multiple parameters separated by comma only when order is
important (e.g. sort).
...which is also inconsistent with multi-valued parameter handling in HTTP :)
I think it doesn't really matter that Solr is inconsistent with HTTP parameter
handling as long as it's consistently inconsistent.
> 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.
