[ https://issues.apache.org/jira/browse/LUCENENET-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy closed LUCENENET-49.
-------------------------
Resolution: Won't Fix
> IndexModifier improvement
> -------------------------
>
> Key: LUCENENET-49
> URL: https://issues.apache.org/jira/browse/LUCENENET-49
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Digy
> Priority: Trivial
> Attachments: IndexModifier.patch
>
>
> I want to propose some extensions for IndexModifier.
> 1- Adding method "AddIndexes" asked by Dave (Sun, 13 May 2007 23:29:37 GMT).
> 2- Adding method "UpdateDocuments".
> ------
> I have a program that performs the below task every night
> for each updated documents
> delete documents(term)
> add document(doc)
> endfor
> But as mentioned in the document
> (http://lucene.apache.org/java/1_9_0/api/org/apache/lucene/index/IndexModifier.html
> "While you can freely mix calls to add() and delete() using this class, you
> should batch you calls for best performance. For example, if you want to
> update 20 documents, you should first delete all those documents, then add
> all the new documents. ")
> it is not a good choise for coding.
> Of course the programming logic can be changed, but i think it could be a
> good solution for everyone to add a performance upgrade to the IndexModifier
> where IndexModifiers defers the "AddDocument" method and continues to
> perform "DeleteDocuments" until some threshold value is reached or it is closed.
> With this patch, my nightly job turns into
> for each updated documents
> UpdateDocuments(term,doc)
> Endfor
> DIGY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|