lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christine Poerschke (JIRA)" <>
Subject [jira] [Commented] (SOLR-11501) Depending on the parser, QParser should not parse local-params
Date Thu, 04 Jan 2018 09:57:00 GMT


Christine Poerschke commented on SOLR-11501:

ticket cross-reference: SOLR-11809 - it seems QueryComponent's {{rq}} parameter parsing can
be affected by this change

> Depending on the parser, QParser should not parse local-params
> --------------------------------------------------------------
>                 Key: SOLR-11501
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: query parsers
>            Reporter: David Smiley
>            Assignee: David Smiley
>             Fix For: 7.2
>         Attachments: SOLR_11501_limit_local_params_parsing.patch, SOLR_11501_limit_local_params_parsing.patch
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message