Return-Path: Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: (qmail 70613 invoked from network); 24 Aug 2010 22:38:57 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 24 Aug 2010 22:38:57 -0000 Received: (qmail 36412 invoked by uid 500); 24 Aug 2010 22:38:56 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 36305 invoked by uid 500); 24 Aug 2010 22:38:55 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 36298 invoked by uid 99); 24 Aug 2010 22:38:55 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Aug 2010 22:38:55 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Aug 2010 22:38:38 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o7OMcG03027441 for ; Tue, 24 Aug 2010 22:38:16 GMT Message-ID: <25638325.543371282689496245.JavaMail.jira@thor> Date: Tue, 24 Aug 2010 18:38:16 -0400 (EDT) From: "Hoss Man (JIRA)" To: dev@lucene.apache.org Subject: [jira] Commented: (SOLR-2087) Dismax handler not handling +/- correctly In-Reply-To: <2157580.538961282681216238.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on 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