Return-Path: Delivered-To: apmail-lucene-solr-user-archive@locus.apache.org Received: (qmail 59932 invoked from network); 23 Sep 2008 21:35:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Sep 2008 21:35:53 -0000 Received: (qmail 19152 invoked by uid 500); 23 Sep 2008 21:35:47 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 19130 invoked by uid 500); 23 Sep 2008 21:35:47 -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 19119 invoked by uid 99); 23 Sep 2008 21:35:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Sep 2008 14:35:47 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [206.190.38.62] (HELO web50308.mail.re2.yahoo.com) (206.190.38.62) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 23 Sep 2008 21:34:46 +0000 Received: (qmail 18173 invoked by uid 60001); 23 Sep 2008 21:34:18 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=TfYeffSM/YJh77+iwHAOQX9qCudW3xve+AfOTopyuGPPSH9wUchA8qhxMi15ZsW8BqEn2tylM+4hx9Mur3UHRXfzwT03NG+X7RdQh3BZksoRnDJ8ecROOKAlpVb3VBjKQLT2I2lKMy4XRQj/w6i0vgg9A2HR7OWEXojX4cPpAMs=; X-YMail-OSG: AvVA3.UVM1mV3iFrz9_UpiAmE5HuPHmtB2Tw3m9TrefsqaXwX7ckIcki66x3eEwOpDg9GBoKIpV4suuKmM8bS6skw4aeQ6ifltBCRYhHHVToXSTl7jJ3hse502NuOmbGIG9v1tdCna3viccBVMW1A8y2CKrlTpD5.NpLI9.HJkICLZZq Received: from [167.206.188.3] by web50308.mail.re2.yahoo.com via HTTP; Tue, 23 Sep 2008 14:34:18 PDT X-Mailer: YahooMailRC/1096.28 YahooMailWebService/0.7.218.2 Date: Tue, 23 Sep 2008 14:34:18 -0700 (PDT) From: Otis Gospodnetic Subject: Re: using BoostingTermQuery To: solr-user@lucene.apache.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <839972.17443.qm@web50308.mail.re2.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org It may be too early to say this.... but I'll say it anyway :) There should be a juicy case study that includes payloads, BTQ, and Spans in the upcoming Lucene in Action 2. I can't wait to see it, personally. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Grant Ingersoll > To: solr-user@lucene.apache.org > Sent: Tuesday, September 23, 2008 5:29:05 PM > Subject: Re: using BoostingTermQuery > > At this point, it's roll your own. I'd love to see the BTQ in Solr > (and Spans!), but I wonder if it makes sense w/o better indexing side > support. I assume you are rolling your own Analyzer, right? Spans > and payloads are this huge untapped area for better search! > > > On Sep 23, 2008, at 5:12 PM, Ensdorf Ken wrote: > > > Hi- > > > > I'm new to Solr, and I'm trying to figure out the best way to > > configure it to use BoostingTermQuery in the scoring mechanism. Do > > I need to create a custom query parser? All I want is the default > > parser behavior except to get the custom term boost from the Payload > > data. Thanks! > > > > -Ken > > -------------------------- > Grant Ingersoll > http://www.lucidimagination.com > > Lucene Helpful Hints: > http://wiki.apache.org/lucene-java/BasicsOfPerformance > http://wiki.apache.org/lucene-java/LuceneFAQ