jira at apache
Nov 23, 2009, 11:18 PM
Post #1 of 1
(93 views)
Permalink
|
|
[jira] Issue Comment Edited: (LUCENE-2086) When resolving deletes, IW should resolve in term sort order
|
|
[ https://issues.apache.org/jira/browse/LUCENE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781806#action_12781806 ]
Uwe Schindler edited comment on LUCENE-2086 at 11/24/09 7:16 AM:
-----------------------------------------------------------------
Just commit it. It is so simple, so if I respin, it can be in 3.0.0.
I did'nt want to have commits in 3.0, because if I respin a release, I would not be able to only take *some* of the fixes into 3.0.0. That was the reason.
Can you put this also in 2.9.2 if you remove the generics?
was (Author: thetaphi):
Just commit it. It is so simple, so if I respin, it can be in 3.0.0.
I did'nt want to have commits in 3.0, because if I respin a release, I would not be able to only take *some* of the fixes into 3.0.0. That was the reason.
> When resolving deletes, IW should resolve in term sort order
> ------------------------------------------------------------
>
> Key: LUCENE-2086
> URL: https://issues.apache.org/jira/browse/LUCENE-2086
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 2.9.2, 3.0.1, 3.1
>
> Attachments: LUCENE-2086.patch
>
>
> See java-dev thread "IndexWriter.updateDocument performance improvement".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene
|
