Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "Nader, John P" <john.nader@cengage.com>
To: "java-user@lucene.apache.org" <java-user@lucene.apache.org>,
	"yonik@lucidimagination.com" <yonik@lucidimagination.com>
Date: Fri, 10 Sep 2010 13:06:25 -0400
Subject: RE: Filters do not work with MultiSearcher?
Thread-Topic: Filters do not work with MultiSearcher?
Thread-Index: ActRBedD3Wru/DPETCa9vA3TEaGuGwABB8NA
Message-ID: <70EA5691BD59734784FF872CD1B9747A15D73E1771@OHCINMBX01.corp.local>
References: <70EA5691BD59734784FF872CD1B9747A15D73E1728@OHCINMBX01.corp.local>
 <AANLkTi=upOeKHyYiqBzcN9zeQ8vmaRmh90E-8uuVJ_GY@mail.gmail.com>
In-Reply-To: <AANLkTi=upOeKHyYiqBzcN9zeQ8vmaRmh90E-8uuVJ_GY@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Thanks.  Now I understand.

We changed my implementation to hold multiple bit sets, one per index reade=
r.  Then we return the correct bit set based upon which reader is being pas=
sed in. =20

The results are exactly what we need.  This is our first use of the MultiSe=
archer (as if that wasn't obvious) and our assumption was that a MultiReade=
r was being passed in.

Thank you for your quick response and useful insights.

-John

-----Original Message-----
From: yseeley@gmail.com [mailto:yseeley@gmail.com] On Behalf Of Yonik Seele=
y
Sent: Friday, September 10, 2010 12:32 PM
To: java-user@lucene.apache.org
Subject: Re: Filters do not work with MultiSearcher?

This is "working as designed".

Note this method:
  public DocIdSet getDocIdSet(IndexReader indexReader) throws IOException {
        return openBitSet;
    }

You must pay attention to the IndexReader passed - and the DocIdSet
returned must always be based on that reader (and the first document
of every reader is always 0).  So returning the same DocIdSet each
time is not valid and will result in errors.

-Yonik
http://lucenerevolution.org  Lucene/Solr Conference, Boston Oct 7-8


On Fri, Sep 10, 2010 at 12:23 PM, Nader, John P <john.nader@cengage.com> wr=
ote:
> We are attempting to perform a filtered search on two indices joined by a=
 MultiSearcher. =A0Unfortunately, it appears there is an issue in the lucen=
e code that is causing the filter to be simply reused at the starting ordin=
al for each individual index instead of being augmented by the starting doc=
ument identifier. =A0We are hoping there is an alternate API that will allo=
w us to perform a filtered search on multiple indices.
>
> For example, we have two indices with three documents each, and a filter =
containing only doc ID 1. =A0When we perform a filtered search on a MultiSe=
archer that joins these two indices, we get two documents back (1, 4), wher=
e we were expecting only the one. =A0This is because the MultiSearcher, ins=
tead of starting at doc ID 3 for the second index, is interpreting the filt=
er individually for each index.
>
> We are using Lucene 3.0.2. =A0The API we see this behavior with is MultiS=
earcher.search(Query, Filter, nDocs) with a MatchAllDocsQuery and the filte=
r code pasted below:
>
> public class OpenBitSetFilter extends Filter {
>
> =A0 =A0private OpenBitSet openBitSet;
>
>
> =A0 =A0public OpenBitSetFilter(OpenBitSet openBitSet) {
> =A0 =A0 =A0 =A0this.openBitSet =3D openBitSet;
> =A0 =A0}
>
> =A0 =A0public DocIdSet getDocIdSet(IndexReader indexReader) throws IOExce=
ption {
> =A0 =A0 =A0 =A0return openBitSet;
> =A0 =A0}
>
> }
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org