lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernhard Messer <Bernhard.Mes...@intrafind.de>
Subject Re: [Jakarta Lucene Wiki] Updated: Lucene2Whiteboard
Date Mon, 16 Aug 2004 21:40:15 GMT
Hi Daniel,

just looked at your changes you made on the whiteboard. You moved the 
"callback interface" idea to "Other Changes". I think that such an 
implementation would raise a change in the current api. Maybe we can 
make the new code backward compatible, but at least, we have to add 
additional methods where a callback object can be passed into classes 
like IndexWriter e.g.

The "logger" idea could be a candidate for "Other Changes". The only 
thing we would have to do is to add a seperate logger class which can be 
adressed from the internal lucene classes, which wouldn't have any 
changes within the api.

best regards
bernhard


lucene-cvs@jakarta.apache.org wrote:

>   Date: 2004-08-11T13:06:28
>   Editor: DanielNaber <daniel.naber@t-online.de>
>   Wiki: Jakarta Lucene Wiki
>   Page: Lucene2Whiteboard
>   URL: http://wiki.apache.org/jakarta-lucene/Lucene2Whiteboard
>
>   TooManyClausesException; move an entry to the other section
>
>Change Log:
>
>------------------------------------------------------------------------------
>@@ -26,6 +26,7 @@
> 
>  9. Add a non-static method isCurrent() to IndexReader and remove static getCurrentVersion()
and lastModified methods: [http://www.mail-archive.com/lucene-dev@jakarta.apache.org/msg06143.html]
> 
>+ 10. Implement an option for error handling described on  the mailing list: [http://www.mail-archive.com/lucene-dev@jakarta.apache.org/msg04050.html
message] - if the TooManyClauses exception is kept, rename it to TooManyClausesException.
> 
> == Other Changes ==
> 
>@@ -33,9 +34,7 @@
> 
>  1. Add support for span queries to query parser?
> 
>- 2. Implement an option for error handling described on  the mailing list: [http://www.mail-archive.com/lucene-dev@jakarta.apache.org/msg04050.html
message]
>-
>- 3. 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.
>+ 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.
> 
> == Schedule ==
> 
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org


Mime
View raw message