On Thu, Aug 4, 2011 at 11:21 AM, wrote:
> Hi Yonik
>
> So I tested the join using the sample data below and the latest trunk. I
> still got the same behaviour.
>
> HOWEVER! In this case it was nothing to do with the patch or solr version. It
> was the tokeniser splitting G1 into G and 1.
Ah, g
ugust 2011 15:04
To: yo...@lucidimagination.com
Cc: solr-user@lucene.apache.org
Subject: RE: Joining on multi valued fields
No I haven't. I will get the latest out of the trunk and report back.
Cheers again,
Matt
-Original Message-
From: ysee...@gmail.com [mailto:ysee...@gmail.com]
bject: Re: Joining on multi valued fields
Hmmm, if these are real responses from a solr server "at rest" (i.e.
documents not being changed between queries) then what you show
definitely looks like a bug.
That's interesting, since TestJoin implements a random test that
should cover ca
t; AN
> B125
> B126
> B130
> BL63
> G41
> GK
> MZ
>
>
>
>
>
> So as you can see I get back 3 results when only 2 match the criteria.
> i.e. docs where G1 is present in multi valued "code" field. Why should
> the last document be incl
From: ysee...@gmail.com [mailto:ysee...@gmail.com] On Behalf Of Yonik
Seeley
Sent: 01 August 2011 18:28
To: solr-user@lucene.apache.org
Subject: Re: Joining on multi valued fields
On Mon, Aug 1, 2011 at 12:58 PM,
wrote:
> I have been using the JOIN patch
> https://issues.apache.org/jira/browse/
On Mon, Aug 1, 2011 at 12:58 PM, wrote:
> I have been using the JOIN patch
> https://issues.apache.org/jira/browse/SOLR-2272 with great success.
>
> However I have hit a case where it doesn't seem to be working. It
> doesn't seem to work when joining to a multi-valued field.
That should work (an
