[jira] [Commented] (SOLR-6113) Edismax doesn't parse well the query uf (User Fields)

["Hoss Man (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019356#comment-14019356 ] 

Hoss Man commented on SOLR-6113:
--------------------------------

bq. I like the idea of removing just the field name, because I agree it gives a better result when I look at it from the permission use case scenario

I think you are overlooking the designed usecase: colons appearing in natural text should be treated as regular text *unless* they are explicitly noted as "special" via the "uf" option.

As yonik pointed out in some recent examples on the mailing list, if a user searches for {{Mission: Impossible}} we should not ignore the {{Mission}} portion of the query string if there is no "Mission" field name and no explicitly configured "Mission" field alias.

the default assumption is that the query string is raw query words -- only if the "uf" options tell us to treat some text as "special" (either a field name or a field alias) should it be treated as special syntax to mean "search in this field" or "serach against this field 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org