[
https://issues.apache.org/jira/browse/LUCENE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420622#comment-13420622
]
Shai Erera commented on LUCENE-4246:
------------------------------------
Still, I don't want to call commit(), then close() every time I want to close.
And I think it will confuse users, i.e. we have close(), commit() and
rollback(). We know what commit() and rollback() do, but what does close()
without commit() does? Is it like rollback()? If so, should we remove
rollback()?
I think that close() doing commit() is fine. Even if it is transactional.
Someone can always call rollback() if he wants to close w/o commit. That's the
purpose of rollback().
> 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: [email protected]
For additional commands, e-mail: [email protected]
