You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/09/28 00:48:03 UTC
[jira] [Commented] (CASSANDRA-6016) Ability to change replication
factor for the trace keyspace
[ https://issues.apache.org/jira/browse/CASSANDRA-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780529#comment-13780529 ]
Jonathan Ellis commented on CASSANDRA-6016:
-------------------------------------------
Does that actually work? I would think this would be a problem:
{code}
public static KSMetaData traceKeyspace()
{
List<CFMetaData> cfDefs = Arrays.asList(CFMetaData.TraceSessionsCf, CFMetaData.TraceEventsCf);
return new KSMetaData(Tracing.TRACE_KS, SimpleStrategy.class, ImmutableMap.of("replication_factor", "1"), true, cfDefs);
}
{code}
Nit: I think you want case-insensitive compare on the allowAlter set.
> Ability to change replication factor for the trace keyspace
> -----------------------------------------------------------
>
> Key: CASSANDRA-6016
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6016
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jeremiah Jordan
> Assignee: Yuki Morishita
> Priority: Minor
> Fix For: 2.0.2
>
> Attachments: 6016-2.0.txt
>
>
> They trace keyspace is currently RF=1, and can't be changed. I want to be able to trace stuff when nodes are down/being stupid.
--
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