On Jan 16, 2007, at 3:55 PM, Michael McCandless wrote:
Doron Cohen wrote:
Michael McCandless <[EMAIL PROTECTED]> wrote on 16/01/2007
12:13:47:
Ning Li wrote:
Re those 2 ideas: I do agree the whole division of certain kinds of
index changes into a reader and other ones into a writer, is confusing
to our users. I think our ideal eventual solution is a single "grand
unified" Index class that efficiently does all things that IndexWriter
and IndexReader do today. (I think this is closest to your 2nd option
in that link).
I'm all for efficiency, but I'd be wary of a grand unifying class
combining Reader/Writer operations as you've already hit the nail on
the head that the reader/writers are too confusing, combining them,
without significant refactoring simplification sounds like it would
just make matters worse since they both already have a fair number of
methods on them. To me, we need to better define what a Reader does
and what a Writer does and make the appropriate changes to the APIs.
--------------------------
Grant Ingersoll
Center for Natural Language Processing
http://www.cnlp.org
Read the Lucene Java FAQ at http://wiki.apache.org/jakarta-lucene/
LuceneFAQ
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
