[
https://issues.apache.org/jira/browse/SOLR-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648421#comment-13648421
]
Jack Krupansky commented on SOLR-4783:
--------------------------------------
Remove it? Why not just disable it for SolrCloud, if that is the immediate
problem?
Rollback seems like a useful, and traditional, feature for me, so I don't quite
grasp what exactly you mean when you ask "Do we really need it?". Can you clue
us in on your thinking? I mean, "rollback" is a traditional function of
database transactions, which is what a sequence of uncommitted updates followed
by a commit seems to be, to me.
And if it is removed from Solr, what "workaround" will you suggest for
situations where a user needs or wants to "roll back" latest, uncommitted
ranges?
In any case, it would be nice to hear more of a discussion about what exactly
is broken and why it can't be readily fixed.
Also, if it is marked as a "major" bug, then maybe the feature is more useful
than you suggest. I mean, you are making it sound as if it is a marginal
feature so that the priority should be "trivial".
> Rollback is not working in SolrCloud
> ------------------------------------
>
> Key: SOLR-4783
> URL: https://issues.apache.org/jira/browse/SOLR-4783
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.2.1
> Environment: AWS Instance
> Linux OS
> Reporter: Shekar R
> Labels: features
> Fix For: 4.2.1
>
>
> I have 4 Solr 4.2.1 and 3 zookeeper cluster with frontend haproxy to Solr
> instances.
> 1. Add a doc (without inline commit and autocommit is disabled in
> solrconfig.xml)
> 2. Issue rollback.
> 3. Again add another doc.
> 4. Issue commit.
> Both docs will be committed.
--
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]
