Thanks Karl. 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?
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? Regards, Rajesh --- Karl Wettin <[EMAIL PROTECTED]> wrote: > Rajesh parab skrev: > > > https://issues.apache.org/jira/browse/LUCENE-879 > > <<Rajesh>> > > As per the hack you mentioned inside JIRA, if some > of > > the documents are deleted and re-inserted into > > secondary index, the other documents inside the > index > > do not change their doc id. However, the newly > added > > documents will have different doc ids and hence, > we > > will have to sync them with primary index doc ids. > Is > > my understanind correct? If this is the case, then > we > > will have to update both the indexes every time > > something inside secondary index changes. > > From the JIRA comments to the second patch in > there: > > This new patch allows consumer to, based on a > primary key, delete a > document and add a new document with the same > document number as the > deleted. The events will occur on merging. > > > 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]
