You are really starting to lose me here Ning...
I think the sentiments are that there are better, less intrusive ways
of doing what you are trying to do with the massive changes to
IndexWriter.
A higher level class that manages the updates can be just as
efficient if not more so, and far simpler as well.
On Jul 12, 2006, at 2:28 PM, Ning Li wrote:
>> The current implementation makes some assumptions, such as the
>> "unique
>> key" is a single field, not any sort of compound key, and it doesn't
>> allow deletes by query. That, coupled with a more complex
>> implementation makes me wary of putting it in IndexWriter.
>
> By "current implementation", you meant Lucene IndexReader in
> general, right?
>
>> I'll rephrase my original question:
>> When implementing NewIndexModifier, what type of efficiencies do we
>> get by using the new protected methods of IndexWriter vs using the
>> public APIs of IndexReader and IndexWriter?
>
> What do you think can be best achieved by using the public APIs of
> IndexReader and IndexWriter?
>
> Regards,
> Ning
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
|