lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Jakarta Lucene Wiki] Updated: Lucene2Whiteboard
Date Tue, 07 Dec 2004 00:19:07 GMT
   Date: 2004-12-06T16:19:06
   Editor: ErikHatcher <>
   Wiki: Jakarta Lucene Wiki
   Page: Lucene2Whiteboard

   no comment

Change Log:

@@ -42,6 +42,8 @@
  2. 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.
+3. Separate Query.toString from the actual conversion to a string representation.  This will
allow custom query parsing implementations to provide their own syntax easily.  This could
be done using an abstract factory that is looked up from each Query.toString implementation,
with the current syntax being provided by QueryParser somehow.
 == Schedule ==
-Release 2.0 may happen sometime in late 2004.  We'll see.
+Release 2.0 may happen sometime in early 2005.  We'll see.

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

View raw message