Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EA2D5D672 for ; Wed, 29 May 2013 14:19:27 +0000 (UTC) Received: (qmail 51834 invoked by uid 500); 29 May 2013 14:19:25 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 51033 invoked by uid 500); 29 May 2013 14:19:24 -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 50979 invoked by uid 99); 29 May 2013 14:19:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 May 2013 14:19:22 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kranti.parisa@gmail.com designates 209.85.214.43 as permitted sender) Received: from [209.85.214.43] (HELO mail-bk0-f43.google.com) (209.85.214.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 May 2013 14:19:17 +0000 Received: by mail-bk0-f43.google.com with SMTP id jm2so3342051bkc.30 for ; Wed, 29 May 2013 07:18:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=WgHW0OFzknRdBidCSV0PLMJbaO2uVpx0oHpqgykFqek=; b=bJ2ZVVVYsVuVDdbWLfdE1g69jzAqx+zMmULHvn9psORhVt0hwxufTrBmovlCrEkMor DnKmAl5D+QyXryUz8MBoRSOm0gkfkOm3YlfOQnfovjwabwDUGmKsKjVKPYUTvKbZzxKy NGVdnyUwIpwb2lYeCMrwuRF1HrF2L+OJd+OskkAO+v3s+CR3cRrGR+ee8TkpMec78pKl 1YLE73WxFBJAJYLn0bx02KRXare4ZFWYhiZmZGca7SsHTCdNlYL4ckmOIUol5UbDZkR/ O5oZWqibiwHzWZPbTE/ZADDXJptkN35I1wSRK8GorcYVbAPoOMVSm3AuVXuqcoX2otfJ IBoA== X-Received: by 10.204.54.204 with SMTP id r12mr753601bkg.132.1369837137113; Wed, 29 May 2013 07:18:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.203.6 with HTTP; Wed, 29 May 2013 07:18:37 -0700 (PDT) In-Reply-To: <1369621177028-4066180.post@n3.nabble.com> References: <1369621177028-4066180.post@n3.nabble.com> From: Kranti Parisa Date: Wed, 29 May 2013 10:18:37 -0400 Message-ID: Subject: Re: Join Queries Scores broken? To: dev@lucene.apache.org Content-Type: multipart/alternative; boundary=001a11c37a06f5669904dddc0f35 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c37a06f5669904dddc0f35 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi David, Initially I posted it on solr-user list and didn't get any reply. I shall try your approach. Thanks & Regards, Kranti K Parisa http://www.linkedin.com/in/krantiparisa On Sun, May 26, 2013 at 10:19 PM, David Smiley (@MITRE.org) < DSMILEY@mitre.org> wrote: > Hi Kranti, > > I think this post belongs on the solr-user list. Any way, Solr join > queries > don't score. Filter queries don't score either so even if join queries > did, > using them in a filter query wouldn't help. For what it's worth, I > implemented a Solr scoring join query for a customer by basing it off of > scoring join query code in Lucene's "join" module. You could do the same= . > My requirements were more extensive but if all I needed was a working > scoring join query, then there isn't that much to it. > > Cheers, > David > > > Kranti=99 K K Parisa wrote > > Hi, > > > > I am trying to score/rank the results based on the boosting values > > specified with the Join queries. > > > > Example: > > http://localhost:8983/solr/masterCore/select?q=3Da*&fq=3D(({!join > > fromIndex=3DchildCore1 > > from=3DparentId to=3Did v=3D$subQ1}) OR ({!join fromIndex=3DchildCore2 > > from=3DauthorId to=3Did > > v=3D$subQ2}))&subQ1=3D(name:xyz^100)&subQ2=3D(author:xyz)&fl=3Did,score > > > > So the matching documents from first join query should be getting highe= r > > score than the ones from the second join query. > > > > But it is not working as expected, do I need to specify any other > > parameters? if it's an issue, shall I create a Jira ticket? > > Thanks & Regards, > > Kranti K Parisa > > http://www.linkedin.com/in/krantiparisa > > > > > > ----- > Author: > http://www.packtpub.com/apache-solr-3-enterprise-search-server/book > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Join-Queries-Scores-broken-tp4065827p4= 066180.html > Sent from the Lucene - Java Developer mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org > For additional commands, e-mail: dev-help@lucene.apache.org > > --001a11c37a06f5669904dddc0f35 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi David,

Initially I posted it on solr-user list and di= dn't get any reply.
I shall try your approach.

=
Thanks & Regards,
Kranti K Parisa



On Sun, May 26, 2013 at 10:19 PM, David = Smiley (@MITRE.org) <DSMILEY@mitre.org> wrote:
Hi Kranti,

I think this post belongs on the solr-user list. =A0Any way, Solr join quer= ies
don't score. =A0Filter queries don't score either so even if join q= ueries did,
using them in a filter query wouldn't help. =A0For what it's worth,= I
implemented a Solr scoring join query for a customer by basing it off of scoring join query code in Lucene's "join" module. =A0You cou= ld do the same.
My requirements were more extensive but if all I needed was a working
scoring join query, then there isn't that much to it.

Cheers,
=A0 David


Kranti=99 K K Parisa wrote
> Hi,
>
> I am trying to score/rank the results based on the boosting values
> specified with the Join queries.
>
> Example:
> http://localhost:8983/solr/masterCore/select= ?q=3Da*&fq=3D(({!join
> fromIndex=3DchildCore1
> from=3DparentId to=3Did v=3D$subQ1}) OR ({!join fromIndex=3DchildCore2=
> from=3DauthorId to=3Did
> v=3D$subQ2}))&subQ1=3D(name:xyz^100)&subQ2=3D(author:xyz)&= fl=3Did,score
>
> So the matching documents from first join query should be getting high= er
> score than the ones from the second join query.
>
> But it is not working as expected, do I need to specify any other
> parameters? if it's an issue, shall I create a Jira ticket?
> Thanks & Regards,
> Kranti K Parisa
> = http://www.linkedin.com/in/krantiparisa





-----
=A0Author: http://www.packtpub.com/apache-solr-3-ent= erprise-search-server/book
--
View this message in context: http:= //lucene.472066.n3.nabble.com/Join-Queries-Scores-broken-tp4065827p4066180.= html
Sent from the Lucene - Java Developer mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


--001a11c37a06f5669904dddc0f35--