[
https://issues.apache.org/jira/browse/SOLR-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
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: https://issues.apache.org/jira/browse/SOLR-2959
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
