Thanks Karl. I think your solution would be useful in case we would like to partition the index into two indexes and use ParallelReader to query both indexes simultaneously.
If this solution is not getting including inside future Lucene releases, what other options we have to update just one of the two indexes and keep doc ids in sync so that we can use ParallelReader? Regards, Rajesh --- Karl Wettin <[EMAIL PROTECTED]> wrote: > Rajesh parab skrev: > > How do we specify the primary key or doc id so > that > > newly added document will use the same doc id. Do > you > > have any sample code that makes use of this patch? > > Sorry, there is only the test case in the patch. > > > > > Secondly, there was a comment saying it is a proof > of > > concept and not a real project. Is anyone using > this > > patch on their production environments? Will this > fix > > get rolled into latest Lucene release? > > I very much doubt this patch would ever be rolled > in. It is just > something I did do see if it was possible to solve > some way without > doing major changes to the core architecture. > > It works though. Feel free to report back in the > issue with any results > you get in case you try it out. > > > karl > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
