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?
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
|