[
https://issues.apache.org/jira/browse/SOLR-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15639937#comment-15639937
]
Yonik Seeley edited comment on SOLR-9733 at 11/5/16 4:34 PM:
-------------------------------------------------------------
I linked SOLR-9682 since it's one of the first examples of a JSON Query (type
"param" which just parses a query from a request parameter).
>From an API POV, the "filter" at the top level should support the exact same
>syntax/semantics as the "filter" within the "domain" block of a JSON Facet.
was (Author: [email protected]):
I linked SOLR-9682 since it's one of the first examples of a JSON Query (type
"param" which just parses a query from a request parameter).
> JSON Request filter param should support queries in JSON syntax
> ---------------------------------------------------------------
>
> Key: SOLR-9733
> URL: https://issues.apache.org/jira/browse/SOLR-9733
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: JSON Request API
> Reporter: Yonik Seeley
>
> Currently, the top level "filter" in the JSON Request API is implemented by
> copying those values back to "fq" parameters, since that is what other
> components currently check.
> We should do a better job of isolating the creation of filters so other
> components don't have to know/care how they were created (i.e. what
> parameters were used, what syntax was used, etc).
> After that, it will be much easier to support filter queries in JSON syntax:
> {
> query : "myquery",
> filter : [ {term : {field:myfield, val:myval} , "another filter" ],
> limit : 10
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
