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

Hoss Man commented on SOLR-911:
-------------------------------

bq. Well, it's optional... it's only an issue for stateless clients without 
conventions or application specific knowledge - and they could always look at 
the original parameters via echoParams.

that assumes it wasn't baked into the config file.

I guess there's no harm in adding it (except perhaps confusion: i'd hate to see 
people assume that they can add "fq=key" since they got "key" back in the 
facet_queries section of the response)

my point was really just that facet constraint "labels" are really only useful 
if each label is easily associated with a way of applying that constraint.  
replacing the query string with a "key" in the response is only useful if that 
key can be used for something.

It seems to me like it would be far more useful to just reserve "key" as a 
special local param that we guarantee will never get used, so people can 
include it in the facet.query and then parse it out of the response themselves. 
 

You can already do this today...

{noformat}
In Config...
    <lst name="defaults">
      <str name="facet.query">{!ignoredparam="Low Price"}price:[* TO 500]</str>
      <str name="facet.query">{!ignoredparam="Hight Price"}price:[500 TO 
*]</str>
      ...
In Query Response...
   <lst name="facet_queries">
     <int name="{!ignoredparam="Low Price"}price:[* TO 500]">3</int>
     <int name="{!ignoredparam="Hight Price"}price:[500 TO *]">0</int>
     ...
{noformat}

...but it would be nice to have a parma name reserved for this.

(admittedly it never occurred to me until this Jira post that that worked, i'm 
going to start encouraging every one i know to start doing that)


> multi-select facets
> -------------------
>
>                 Key: SOLR-911
>                 URL: https://issues.apache.org/jira/browse/SOLR-911
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>            Reporter: Yonik Seeley
>             Fix For: 1.4
>
>         Attachments: SOLR-911.patch, SOLR-911.patch, SOLR-911.patch
>
>
> plumbing to support the selection of multiple constraints in a facet

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to