You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mikhail Khludnev (JIRA)" <ji...@apache.org> on 2018/06/14 14:34:00 UTC
[jira] [Updated] (SOLR-9733) JSON Request filter param should
support queries in JSON syntax
[ https://issues.apache.org/jira/browse/SOLR-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Khludnev updated SOLR-9733:
-----------------------------------
Description:
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:
{code}
{
query : "myquery",
filter : [ {term : {field:myfield, val:myval}} , "another filter" ],
limit : 10
}
{code}
was:
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
}
> 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
> Priority: Major
>
> 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:
> {code}
> {
> query : "myquery",
> filter : [ {term : {field:myfield, val:myval}} , "another filter" ],
> limit : 10
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org