[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420884#comment-13420884
]
Shai Erera commented on LUCENE-4246:
------------------------------------
I still don't understand why change behavior that is out there for ages.
Everyone is used to calling close() and that commits things. I agree with you
that if from the beginning people would need to call commit() before close(),
then that's better. But I don't think there is a good justification to change
current behavior.
Now you're talking about detecting whether there were any changes or not --
that doesn't simplify close() logic IMO.
In short, I don't feel that changing current behavior is going to do any good,
on the contrary, it would confuse people.
> Fix IndexWriter.close() to not commit or wait for pending merges
> ----------------------------------------------------------------
>
> Key: LUCENE-4246
> URL: https://issues.apache.org/jira/browse/LUCENE-4246
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Assignee: Robert Muir
> Fix For: 4.0
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
