lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eyal Zaidman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-6113) Edismax doesn't parse well the query uf (User Fields)
Date Wed, 28 May 2014 09:03:02 GMT

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

Eyal Zaidman commented on SOLR-6113:
------------------------------------

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 - you get to search where you're allowed,
and there's a chance your data is in the default search field.
A literal search with the field name in that scenario would likely suffer from the original
issue - there is very little chance the field name exists, as the user did not intend to look
for it.

I also agree that it's important to provide feedback that search results have been changed,
but it seems to me if the search client is adding a uf restriction, it should be the clients
responsibility to inform the end user about that restriction ? or at least I can't come up
with a good way for Solr to do that.

> 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


Mime
View raw message