[
https://issues.apache.org/jira/browse/SOLR-9682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644430#comment-15644430
]
Yonik Seeley commented on SOLR-9682:
------------------------------------
I considered that, but he long view is that a filter is a list of queries in
JSON Query Syntax (there's an old issue open, never got to finish it),
and a string is a query in lucene/solr syntax. So for maximum consistency, one
would then want to change lucene/solr syntax to accept "$myFilterParam" as well.
If not, one would then need to escape queries differently depending on if they
will be used in something like "fq" vs "filter".
> 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
> Fix For: master (7.0), 6.4
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
