lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Jakarta Lucene Wiki] Updated: Lucene2Whiteboard
Date Mon, 09 Aug 2004 07:29:28 GMT
   Date: 2004-08-09T00:29:28
   Editor: BernhardMesser <>
   Wiki: Jakarta Lucene Wiki
   Page: Lucene2Whiteboard

   no comment

Change Log:

@@ -30,6 +30,7 @@
  11. Remove public PrintStream infoStream from IndexWriter and System.out.println() from
TermVectorsReader. Instead use some kind of Logger which is customizable thru the API to print
debug, error and warning messages within lucene. The logger must not be an external library
like log4j, it could be a small implementation directly in lucene to avoid references to external
+ 12. Implement a callback interface for processes which can run for several minutes like
IndexWriter.optimize(). The idea is to define a simple public interface which can be implemented
by developers using lucene. The object implementing the callback, could be passed to methods
like optimize() and can inform the caller when one of the steps to process has finished. This
would make it much easier in interactive applications to inform the user that the system is
working and not frozen.
 == Schedule ==

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message