"Chris Hostetter" <[EMAIL PROTECTED]> wrote: > > I've never really used the setInfoStream feature of IndexWriter, but the > recent discussion about silent exceptions in ConcurrentMergeScheduler got > me noticing that the code has it's own message(...) method that writes to > System.out ... would it make sense to expose the IndexWriter's > infostream? > either by making IndexWRiter.message publicly accessible or by having the > IndexWriter pass it directly to the MergeScheduler and MergePolicy?
+1 I'll do this. IndexWriter already shares its infoStream with IndexFileDeleter and DocumentsWriter, so I'll fix it to do the same with MergePolicy & MergeScheduler. Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
