You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Arcadius Ahouansou (JIRA)" <ji...@apache.org> on 2015/06/08 14:05:01 UTC

[jira] [Commented] (SOLR-4733) Rollback does not work correctly with tlog and optimistic concurrency updates

    [ https://issues.apache.org/jira/browse/SOLR-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577088#comment-14577088 ] 

Arcadius Ahouansou commented on SOLR-4733:
------------------------------------------

Any progress on this issue?
Having rollback() in SolrCloud would be a very usefuly feature.
IMHO, a rolling back all uncommited changes from other clients is OK as it is consistent with the way commit() works at the moment.

> 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.2.1, 4.3
>         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 was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org