Yonik Seeley wrote on 07/10/2006 09:27 AM: > I'll rephrase my original question: > When implementing NewIndexModifier, what type of efficiencies do we > get by using the new protected methods of IndexWriter vs using the > public APIs of IndexReader and IndexWriter?
I won't comment on Ning's implementation, but will comment wrt this issue for related work I've done with bulk update. I needed at least package-level access to several of the private capabilities in the index package (e.g., from SergmentMerger: resetSkip(), bufferSkip(), writeSkip(); from IndexWriter: readDeletableFiles(), writeDeletableFiles(); etc.). I think the index package and its api's have not been designed from the standpoint of update (batched delete/add or bulk), and are not nearly as friendly to application-level specialization/customization as other parts of Lucene. As part of the new index representation being considered now, I hope that these issues are addressed, and would be happy to participate in addressing them (especially if gcj releases 1.5 and 1.5 code becomes acceptable). Chuck --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
