Return-Path: Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: (qmail 49102 invoked from network); 13 Apr 2010 14:15:40 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Apr 2010 14:15:40 -0000 Received: (qmail 11932 invoked by uid 500); 13 Apr 2010 14:15:37 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 11867 invoked by uid 500); 13 Apr 2010 14:15:37 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 11858 invoked by uid 99); 13 Apr 2010 14:15:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Apr 2010 14:15:37 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=AWL,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gsiasf@gmail.com designates 209.85.221.197 as permitted sender) Received: from [209.85.221.197] (HELO mail-qy0-f197.google.com) (209.85.221.197) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Apr 2010 14:15:31 +0000 Received: by qyk35 with SMTP id 35so6608952qyk.11 for ; Tue, 13 Apr 2010 07:15:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:content-type :mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=3R0nLmAwloAw+F02QFGk8OJ+6a1oaRYhuVzm5kwYozM=; b=SEI0h9ldLSWkskKI3+8KseGng8nRP1dPr93Nxwi8ljifH1CrWZ+16g/1qVMCmnCLb+ klQtejhffPKq4ydlKWjZJWCsCwMvl1NUdVzkMgz+2wzvJOmGdOLD8mXuWtd6Sv3emReN e1MwErrxRtczb6evW4Ep+SRIMm5wZRwa1b1c0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=cSWNzbbBHCnd6iyaPEdHNSRPbfypX8KY3Aw4vJoUvoM52tVBrp5WdnJ32nFIIIX9oI seXUb68xZ68u6rSqSK/u8DwGUepkH8k5sw6j8LKYT8WkK3ba+t/FE9CFPNX6znRXFToY Jl6rsEUc3Od3WrX/BuvJXa2INeD8Iuf6xr7M8= Received: by 10.224.78.104 with SMTP id j40mr2065555qak.251.1271168110142; Tue, 13 Apr 2010 07:15:10 -0700 (PDT) Received: from [10.0.0.77] (adsl-065-013-152-164.sip.rdu.bellsouth.net [65.13.152.164]) by mx.google.com with ESMTPS id v26sm7602398qce.7.2010.04.13.07.15.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 13 Apr 2010 07:15:09 -0700 (PDT) Sender: Grant Ingersoll Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1078) Subject: Re: closest terms, sentence, boosting 'business' keywords instead of field ? From: Grant Ingersoll In-Reply-To: Date: Tue, 13 Apr 2010 10:15:07 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <76A5B03E-E5A6-43A3-8369-CA6BE2FB1D95@apache.org> References: To: solr-user@lucene.apache.org X-Mailer: Apple Mail (2.1078) On Apr 13, 2010, at 10:02 AM, Abdelhamid ABID wrote: >>=20 >> Do you have an example of what you are trying to do? >>>>=20 >>>>=20 >=20 >=20 > For instance a request like: "tomcat servlet" should return document = which >>>>>>> have "tomcat is a servlet container" rather than a document that = have"tomcat offers the last specification implementaion of the servlet >>>>>>> technology", at least this last should not come before the = first in >>>>>>> results. >>>>>>=20 >>>>>>=20 >=20 Using a phrase query with a high slop value should handle this, as the = closer the terms are, the better the score for that match. >=20 >> Boost in the query or during indexing? >>>>=20 >>>>=20 > I think boosting in query is more relevant. >>>>>>=20 >>>>>>=20 > Thanks >=20 >=20 >=20 >=20 > On 4/13/10, Grant Ingersoll wrote: >>=20 >>=20 >> On Apr 12, 2010, at 7:57 PM, Abdelhamid ABID wrote: >>=20 >>> Hi, >>> - I'm bit confused on how analyzer apply filters on query, I know = that >> they >>> are applied in order on which they are declared, but still, does the >> search >>> result >>> include only the final digest of the filters chain or at each filter = step >>> solr add the matched term to results set. >>=20 >>=20 >> It is the final output. >>=20 >>=20 >>>=20 >>> - Does Dismax request handler support quoted keywords ? if not, how = can I >>> search for an exact sentence using dismax. >>=20 >>=20 >> It does. >>=20 >>=20 >>> - How to match a request with the documents that only have keywords = that >>> appears in the closest positions. >>=20 >>=20 >> Do you have an example of what you are trying to do? >>=20 >>=20 >>> - How can I boost a set of keywords instead of fields? this would be >> useful >>> in case where a document with one single searchable field, which is = of >> type >>> text and where "boosting field" has no sense. >>=20 >>=20 >> Boost in the query or during indexing? You should be able to just boost the keyword using the ^ operator. =20 >>=20 >>=20 >> -------------------------- >> Grant Ingersoll >> http://www.lucidimagination.com/ >>=20 >> Search the Lucene ecosystem using Solr/Lucene: >> http://www.lucidimagination.com/search >>=20 >>=20