Chris Bannister created CASSANDRA-11099:
---
Summary: Prepared metadata does not include CAS applied column
Key: CASSANDRA-11099
URL: https://issues.apache.org/jira/browse/CASSANDRA-11099
Project:
Wei Deng created CASSANDRA-11100:
Summary: nodetool command to rebalance the cluster in 3.0+
Key: CASSANDRA-11100
URL: https://issues.apache.org/jira/browse/CASSANDRA-11100
Project: Cassandra
[
https://issues.apache.org/jira/browse/CASSANDRA-9660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
pankaj mishra reassigned CASSANDRA-9660:
Assignee: pankaj mishra
> erro while adding a node to existing cluster
>
[
https://issues.apache.org/jira/browse/CASSANDRA-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15125166#comment-15125166
]
mck commented on CASSANDRA-10392:
-
> Could you rebase the C* patch against trunk? then I can kick off
[
https://issues.apache.org/jira/browse/CASSANDRA-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mck updated CASSANDRA-10392:
Attachment: 10392-trunk.txt
> Allow Cassandra to trace to custom tracing implementations
>
[
https://issues.apache.org/jira/browse/CASSANDRA-11100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15125103#comment-15125103
]
Brandon Williams commented on CASSANDRA-11100:
--
See CASSANDRA-7601 for the pitfalls here
[
https://issues.apache.org/jira/browse/CASSANDRA-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mck updated CASSANDRA-10392:
Attachment: (was: 10392-trunk.txt)
> Allow Cassandra to trace to custom tracing implementations
>
Sharvanath Pathak created CASSANDRA-11101:
-
Summary: Yammer metrics upgrade required
Key: CASSANDRA-11101
URL: https://issues.apache.org/jira/browse/CASSANDRA-11101
Project: Cassandra
