lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SOLR-6113) Edismax doesn't parse well the query uf (User Fields)
Date Tue, 27 May 2014 22:44:02 GMT

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

Jan Høydahl commented on SOLR-6113:
-----------------------------------

Suggestion for improvements welcome. In my opinion, simply discarding the whole term is also
very confusing. Imagine {{uf=-title&q=title:java language}} -> as we're now you will
require the three words title, java, language. If we remove the first term we'll match all
docs with "language", clearly not the intention.

A perhaps better solution could be to search literally for the string "title:java" instead
of breaking it into two?

Alternatively, disregard the "field" part, but let the value part stay and be subject to qf
or df. However, that could be confusing too, if the user won't get any feedback whatsoever
that his query term "java" was actually not restricted to title only.

> 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
>              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