[
https://issues.apache.org/jira/browse/SOLR-9682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759171#comment-16759171
]
Yonik Seeley commented on SOLR-9682:
------------------------------------
> What it someone make a typo when attempting to filter out some explicit
> content?
If someone adds a filter and it doesn't work, the filter (and how it's
specified via param) will be the first thing they look at (hence a typo should
be easy to debug). Removing a feature to allow detecting of one very specific
typo doesn't seem like a good trade-off in this specific scenario.
It's a common scenario to want to filter if one is provided. It makes it
easier to have a request that doesn't have to be modified as much based on the
absence/presence of other parameters.
Also, "Multi-valued parameters should be supported." was part of the objective.
So the parameter refers to a list of filters... and allowing "0 or more" for a
list is more flexible than "you're not allowed to have a 0 length list".
> Ability to specify a query with a parameter name (in facet filter)
> ------------------------------------------------------------------
>
> Key: SOLR-9682
> URL: https://issues.apache.org/jira/browse/SOLR-9682
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Facet Module
> Reporter: Yonik Seeley
> Assignee: Yonik Seeley
> Priority: Major
> Fix For: 6.4, 7.0
>
> Attachments: SOLR-9682.patch
>
>
> Currently, "filter" only supports query strings (examples at
> http://yonik.com/solr-json-request-api/ )
> It would be nice to be able to reference a param that would be parsed as a
> lucene/solr query. Multi-valued parameters should be supported.
> We should keep in mind (and leave room for) a future "JSON Query Syntax" and
> chose labels appropriately.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
