[
https://issues.apache.org/jira/browse/SOLR-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673741#comment-13673741
]
Yonik Seeley commented on SOLR-4733:
------------------------------------
Rollback is never going to be a "first class" feature... there's no transaction
isolation, so it only going to make sense for people that have complete control
/ coordination over all indexing clients. If that's the case, optimistic
concurrency isn't needed.
I think we can improve rollback support by dropping all the internal tlog state
and forcing open a new realtime reader (basically, what the delete-by-query
code does), but that's probably the extent of it. The vast majority of people
should not use "rollback".
> Rollback does not work correctly with tlog and optimistic concurrency updates
> -----------------------------------------------------------------------------
>
> Key: SOLR-4733
> URL: https://issues.apache.org/jira/browse/SOLR-4733
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.3, 4.2.1
> Environment: Ubuntu 12.04.2 LTS
> Reporter: Mark S
> Labels: solrj
> Attachments: SOLR-4733.patch
>
>
> When using the updateLog, attempting to rollback atomic updates still causes
> post-rollback atomic updates to still report a conflict with the version
> assigned to the update posted prior to the rollback
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
