[
https://issues.apache.org/jira/browse/CASSANDRA-9564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14578403#comment-14578403
]
Peter van der Velde edited comment on CASSANDRA-9564 at 6/9/15 6:34 AM:
------------------------------------------------------------------------
[~beobal] I have downloaded the 2.0.15 sources and applied the patch and ran an
ant build. The resulting 2.0.15-snapshot jar files copied into the lib folder
of a 2.0.15 binary download(removed the 2.0.15 jars). Started this cassandra
instance and ran the problematic scenario: and the result is as expected!
To be sure I created the pacthed build correctly I started an original 2.0.15
release to confirm the issue was still present in this version(and it was).
was (Author: peterv):
[~beobal] I have downloaded the 2.0.15 sources and applied the patch and ran a
ant build. The resulting 2.0.15-snapshot jar files copied into the lib folder
of a 2.0.15 binary download(removed the 2.0.15 jars). Started this cassandra
instance and ran the problematic scenario: and the result is as expected!
To be sure I created the pacthed build correctly I started an original 2.0.15
release to confirm the issue was still present in this version(and it was).
> Backport CASSANDRA-9057 to 2.0
> ------------------------------
>
> Key: CASSANDRA-9564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9564
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Fix For: 2.0.16
>
> Attachments: 9564.txt
>
>
> It seems that the issue described in CASSANDRA-9057 also manifests on the 2.0
> branch, so we should backport the fix from 2.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
