You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Gabriel Weinberg (JIRA)" <ji...@apache.org> on 2010/08/24 22:20:16 UTC
[jira] Created: (SOLR-2087) Dismax handler not handling +/-
correctly
Dismax handler not handling +/- correctly
-----------------------------------------
Key: SOLR-2087
URL: https://issues.apache.org/jira/browse/SOLR-2087
Project: Solr
Issue Type: Bug
Components: search
Affects Versions: 1.4
Reporter: Gabriel Weinberg
If I do a query like: i'm a walking contradiction it matches pf as text:"i'm_a a_walking walking contradiction"^2.0, and it matches fine.
If I do a query like: i'm a +walking contradiction it matches pf as text:"i'm_a a_+walking +walking contradiction"^2.0 and doesn't match at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (SOLR-2087) Dismax handler not handling +/-
correctly
Posted by "Gabriel Weinberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902126#action_12902126 ]
Gabriel Weinberg commented on SOLR-2087:
----------------------------------------
Hoss, thanks for clarifying, but I'm still a bit confused.
What I had in mind was that this current behavior breaks anything but a blank mm field. That is, if either the user (or I on the backend) mark any fields as mandatory or prohibited, the pf is rendered useless. Is that what you mean by intended behavior?
I will try the tokenizer suggestion though.
> Dismax handler not handling +/- correctly
> -----------------------------------------
>
> Key: SOLR-2087
> URL: https://issues.apache.org/jira/browse/SOLR-2087
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.4
> Reporter: Gabriel Weinberg
>
> If I do a query like: i'm a walking contradiction it matches pf as text:"i'm_a a_walking walking contradiction"^2.0, and it matches fine.
> If I do a query like: i'm a +walking contradiction it matches pf as text:"i'm_a a_+walking +walking contradiction"^2.0 and doesn't match at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (SOLR-2087) Dismax handler not handling +/-
correctly
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902119#action_12902119 ]
Hoss Man commented on SOLR-2087:
--------------------------------
It's possible some improvements could be made here, but this is functioning as originally designed.
the pf param treats the entire q param as one big quoted phrase, without any special consideration of other markup, in order to give a boost to things that *exactly* match the users input in any of the pf fields. (ie: users cut/paste an exact line of text from the content they are looking for.
in your use case, it might make sense to use an alternate tokenizer in the fields you want to use in your "pf" (perhaps something that tokenizes away the leading "+/-" characters) but there are other uses cases where people have content that includes those characters, and they want the phrase boosting part of the query to account for them.
> Dismax handler not handling +/- correctly
> -----------------------------------------
>
> Key: SOLR-2087
> URL: https://issues.apache.org/jira/browse/SOLR-2087
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.4
> Reporter: Gabriel Weinberg
>
> If I do a query like: i'm a walking contradiction it matches pf as text:"i'm_a a_walking walking contradiction"^2.0, and it matches fine.
> If I do a query like: i'm a +walking contradiction it matches pf as text:"i'm_a a_+walking +walking contradiction"^2.0 and doesn't match at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org