[
https://issues.apache.org/jira/browse/SOLR-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17792123#comment-17792123
]
Dawid Weiss commented on SOLR-16916:
------------------------------------
I just hit this one and it seems like a regression to me - everything worked up
until 9.3.0. Queries are strings (in JSON requests), but the default query
parser is switched to a different one in solrconfig.xml:
{code:java}
<str name="defType">customParser</str> {code}
After upgrading to 9.4.0, the server seems to ignore this parameter completely
and fails to parse queries.
> JSON Query DSL doesn't work if defType isn't lucene
> ---------------------------------------------------
>
> Key: SOLR-16916
> URL: https://issues.apache.org/jira/browse/SOLR-16916
> Project: Solr
> Issue Type: Bug
> Components: query parsers
> Affects Versions: 7.2
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Fix For: 9.4
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> If the [JSON Query DSL|https://solr.apache.org/guide/8_4/json-query-dsl.html]
> is used (POSTing JSON), it requires that the default "lucene" query parser is
> used. If for some reason defType is set, like in the defaults section of the
> request handler, then this doesn't work. Internally, the JSON is rewritten
> to local-params syntax which requires the default parser, not another like
> edismax.
> This behavior broke in 7.2 when other parsers stopped processing local-params
> in the name of security.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
