[
https://issues.apache.org/jira/browse/SOLR-9682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15600352#comment-15600352
]
Yonik Seeley commented on SOLR-9682:
------------------------------------
example:
{code}
curl 'http://localhost:8983/solr/query?myfilter=user:Yonik+rating:5' -d '
{
query : "awesome",
limit : 10,
filter : { queryParam : myfilter }
}'
{code}
When we finally get around to specifying a complete query language in JSON,
we'll want this to slide right in. So think of "queryParam" as the type of the
query. The value is retrieved from "params" and parsed as a lucene/solr query.
paramToSolrQuery would be more exact/descriptive, but too long and awkward to
remember exactly.
"deref" or "dereference" ?
> Ability to specify a query with a parameter name
> ------------------------------------------------
>
> 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, JSON Request API
> Reporter: Yonik Seeley
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
