You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2017/10/19 16:22:00 UTC
[jira] [Assigned] (SOLR-11501) Depending on the parser,
QParserPlugin should not parse local-params
[ https://issues.apache.org/jira/browse/SOLR-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley reassigned SOLR-11501:
-----------------------------------
Assignee: David Smiley
> Depending on the parser, QParserPlugin should not parse local-params
> --------------------------------------------------------------------
>
> Key: SOLR-11501
> URL: https://issues.apache.org/jira/browse/SOLR-11501
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: query parsers
> Reporter: David Smiley
> Assignee: David Smiley
>
> Solr should not parse local-params (and thus be able to switch the query parser) in certain circumstances. _Perhaps_ it is when the QParser.getParser is passed "lucene" for the {{defaultParser}}? This particular approach is just a straw-man; I suspect certain valid embedded queries could no longer work if this is done incorrectly. Whatever the solution, I don't think we should assume 'q' is special, as it's valid and useful to build up queries containing user input in other ways, e.g. {{q= +field:value +\{!dismax v=$qq\}&qq=user input}} and we want to protect the user input there similarly from unwelcome query parsing switching.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org