[
https://issues.apache.org/jira/browse/CASSJAVA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18040392#comment-18040392
]
Bret McGuire commented on CASSJAVA-118:
---------------------------------------
This ticket was created form an internal DataStax ticket that wound up assigned
to the wrong JIRA. I've confirmed that the comment in question [is still
present|https://github.com/apache/cassandra-java-driver/blob/4.19.2/core/src/main/java/com/datastax/dse/driver/api/core/graph/BatchGraphStatement.java#L33-L34].
> BatchGraphStatement documentation page of DSE Java Driver needs update
> ----------------------------------------------------------------------
>
> Key: CASSJAVA-118
> URL: https://issues.apache.org/jira/browse/CASSJAVA-118
> Project: Apache Cassandra Java driver
> Issue Type: Improvement
> Components: Core
> Reporter: Bret McGuire
> Priority: Normal
>
> [https://docs.datastax.com/en/drivers/java/latest/com/datastax/dse/driver/api/core/graph/BatchGraphStatement.html]
> {quote}All the mutations grouped in the batch will either all succeed, or
> they will all be discarded and return an error.
> {quote}
> This statement is wrong after the implementation of Core engine in DSE Graph.
> It holds TRUE only for the Classic engine.
> In the Core engine, commit happens after each traversal and there is no kind
> of rollback mechanism written. So, if a failure happens in the middle, all
> the previously executed commands wouldn’t be rolled back even if the request
> is via BatchGraphStatement. The mutations need to be manually cleared if
> required.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
