lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tobias Krönke (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-11501) Depending on the parser, QParser should not parse local-params
Date Mon, 15 Jan 2018 18:23:00 GMT

    [ https://issues.apache.org/jira/browse/SOLR-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326494#comment-16326494
] 

Tobias Krönke edited comment on SOLR-11501 at 1/15/18 6:22 PM:
---------------------------------------------------------------

The docs and this changelog always suggest to use a comma in the {{uf}} parameter to allow
multiple fields. By experiment, that seems to be false. You need to separate the fields with
a space, e.g. {{uf=_query_ *}}


was (Author: tuky):
The docs and this changelog always suggest to use a comma in the {{uf}} parameter to allow
multiple fields. By experiment, that seems to be false. You need to separate the fields with
a space.

> Depending on the parser, QParser 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
>            Priority: Major
>             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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message