[
https://issues.apache.org/jira/browse/CASSANDRA-8592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353171#comment-14353171
]
Tyler Hobbs commented on CASSANDRA-8592:
----------------------------------------
Oh, it just occurred to me that the driver will also need to support
WriteFailureException for that to work in the dtest. We _could_ monkey-patch
support for that inside the test class, but we always have this problem with
protocol changes, and it would be nice to have a better solution.
[~philipthompson] should we consider using a fork of the python driver for
dtests runs? Or perhaps specify a git branch to use for the run? That would
be a little tricky, because you'd need to modify {{sys.path}} after checking
out a branch (in the dtest setup), but I think it could work.
> Add WriteFailureException
> -------------------------
>
> Key: CASSANDRA-8592
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8592
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Tyler Hobbs
> Assignee: Stefania
> Labels: client-impacting
> Fix For: 3.0
>
>
> Similar to what CASSANDRA-7886 did for reads, we should add a
> WriteFailureException and have replicas signal a failure while handling a
> write to the coordinator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
