lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Wolanin (JIRA)" <>
Subject [jira] [Commented] (SOLR-4197) EDismax allows end users to use local params in q= to override global params
Date Mon, 17 Dec 2012 04:40:12 GMT


Peter Wolanin commented on SOLR-4197:

Apparently adding a space at the beginning is not a complete solution - I then get an exception
when it's the standard lucene parser:
Problem accessing /solr/select. Reason:

    org.apache.lucene.queryParser.ParseException: Cannot parse ' {!lucene}hello': Encountered
" "}" "} "" at line 1, column 9.
Was expecting one of:
    "TO" ...
    <RANGEEX_GOOP> ...
> EDismax allows end users to use local params in q= to override global params
> ----------------------------------------------------------------------------
>                 Key: SOLR-4197
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 3.5, 3.6, 4.0
>            Reporter: Peter Wolanin
> Edismax is advertised as suitable to be used to "process advanced user input directly".
 Thus, it would seem reasonable to have an application directly pass user input in the q=
parameter to a back-end Solr server.
> However, it seems that users can enter local params at the start of q= which override
the global params that the application (e.g. website) may have set on the query string.  Confirmed
with Erik Hatcher that this is somewhat unexpected behavior (though one could argue it's an
expected feature of any query parser)
> Proposed fix - add a parameter (e.g. that can be used as an invariant) that can be passed
to inhibit Solr from using local params from the q= parameter.
> This is somewhat related to SOLR-1687

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

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

View raw message