[
https://issues.apache.org/jira/browse/SOLR-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009465#comment-14009465
]
Jan Høydahl commented on SOLR-6113:
-----------------------------------
It is actually by design, if you e.g. disallow all fielded search with
{{&uf=-*}} then eDismax will not interpret the x:y as field and value but as a
valid query for literal x y. Some languages use : as separator, e.g. swedish
will write {{FN:s}} (meaning UN's). The same approach is taken when some field
names are disallowed.
But I see that it can be confusing for people who indend to search a field, it
would be better if Solr could give a feedback that fielded search is not
allowed and that it falled back to literal matching.
> Edismax doesn't parse well the query uf (User Fields)
> -----------------------------------------------------
>
> Key: SOLR-6113
> URL: https://issues.apache.org/jira/browse/SOLR-6113
> Project: Solr
> Issue Type: Bug
> Components: query parsers
> Reporter: Liram Vardi
>
> It seems that Edismax User Fields feature does not behave as expected.
> For instance, assuming the following query:
> _"q= id:b* user:"Anna Collins"&defType=edismax&uf=* -user&rows=0"_
> The parsed query (taken from query debug info) is:
> _+((id:b* (text:user) (text:"anna collins"))~1)_
> I expect that because "user" was filtered out in "uf" (User fields), the
> parsed query should not contain the "user" search part.
> In another words, the parsed query should look simply like this: _+id:b*_
> This issue is affected by a the patch on issue SOLR-2649: When changing the
> default OP of Edismax to AND, the query results change.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
