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 Tue, 27 May 2014 13:50:02 GMT

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

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

I'm a little confused by that behavior, assuming I understand the technical details. The real
world scenario uf is trying to address is disallowing or restricting search in some fields,
so for example if I wanted to implement a permissions scheme, I could tell it -restrictedField
and it would not search there. By treating that search as a literal (presumably because we
can't detect whether the user meant a fielded search or a Swedish term, exactly matching a
SOLR field name) we're preferring the less common to rather esoteric (IMO) scenario.
Adding to that Liram's comment about the relation to SOLR-2649, the default operator behavior
could make this even worse, where instead of OR you get an AND behavior, and all searches
fail due to forcing a non-existent literal match.

Do you think it would make sense to add functionality that removes that part of the search
query instead of escaping it ? We could of course make some flag for preserving the old behavior
in case someone finds it useful.

Could you point us in the right direction to do it if so ? We'd be happy to attempt a patch

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message