Ids and so the
> next
> > > > step is either collate the 100 docIds into a query with OR, or do a
> > > > searcher.search() for 100 times.
> > > >
> > > > Fine, if it isn't very expensive.
> > > >
> > > > On a slightly related note, stumbled upon this
> > > Fine, if it isn't very expensive.
> > >
> > > On a slightly related note, stumbled upon this thread
> > >
> > >
> >
> http://lucene.472066.n3.nabble.com/App-supplied-docID-in-lucene-possible-td4015797.htmlas
> > > well. Some good
upon this thread
> >
> >
> http://lucene.472066.n3.nabble.com/App-supplied-docID-in-lucene-possible-td4015797.htmlas
> > well. Some good discussion on this.
> >
> > >
> > > --
> > > Ian.
> > >
> > >
> > > On Fri, Mar 1
sible-td4015797.htmlas
> well. Some good discussion on this.
>
> >
> > --
> > Ian.
> >
> >
> > On Fri, Mar 1, 2013 at 9:51 AM, Ramprakash Ramamoorthy
> > wrote:
> > > Hello team,
> > >
> > > I have a query and I am explaining
>
> On Fri, Mar 1, 2013 at 9:51 AM, Ramprakash Ramamoorthy
> wrote:
> > Hello team,
> >
> > I have a query and I am explaining it as below.
> >
> > Objective : To split index and store, and combine it during query time
> >
> > Approach
Never rely on lucene internal doc ids. Use your own. Lucene searches
on unique ids are of course very fast.
--
Ian.
On Fri, Mar 1, 2013 at 9:51 AM, Ramprakash Ramamoorthy
wrote:
> Hello team,
>
> I have a query and I am explaining it as below.
>
> Objective : To
