lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (Updated) (JIRA)" <>
Subject [jira] [Updated] (SOLR-2959) edismax consider magic fields '_query_' and '_val_'
Date Tue, 20 Mar 2012 19:27:38 GMT


Hoss Man updated SOLR-2959:

    Attachment: SOLR-2959.patch

Michael: thanks for your patch.

the situation has changed a bit since you opend this issue, particularly with regards to SOLR-3026
and the new support for specifying exactly which fields can/can't be used in the query string.

it appears that at the moment, (trunk) edismax supports _val_ and _query_ just fine -- and
in fact the bug is sort of the reverse of before: you can't use the uf param to prevent them
from working.

I've expanded on your test changes to demonstrate this in the update attachment.  will tweak
issue summary shortly
> edismax consider magic fields '_query_' and '_val_'
> ---------------------------------------------------
>                 Key: SOLR-2959
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: query parsers
>            Reporter: Michael Watts
>            Priority: Minor
>             Fix For: 3.6
>         Attachments: SOLR-2959.patch, SOLR-2959.patch
> The edismax query parser should recognize '\_query\_' and '\_val\_' as so-called magic
fields  rather un-prefixed query text.

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


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

View raw message