[
https://issues.apache.org/jira/browse/SOLR-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021161#comment-14021161
]
Eyal Zaidman commented on SOLR-6113:
------------------------------------
Please excuse my continued confusion, I'm still a bit new to the technical
aspects of this feature - I assumed Jan's suggestion was referring to excluding
the field name for an *existing* field specified in uf, so for your example
"q=Mission: Impossible&uf=* -Mission" would indeed search for just Impossible,
because there is a Mission field/alias defined.
Yonik was replying as to why edismax would not throw an exception when uf
disallows something, and that seems very reasonable. Are you referring to the
same use case as above, where Mission is not a field ? meaning I specify
something in uf that isn't a field or an alias?
> 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: Improvement
> Components: query parsers
> Reporter: Liram Vardi
> Priority: Minor
> Labels: edismax
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
