cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (CASSANDRA-1021) no way to define a schema on boot
Date Sat, 24 Apr 2010 20:17:50 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis reassigned CASSANDRA-1021:
-----------------------------------------

    Assignee: Gary Dusbabek

It's supposed to pull the schema from an existing node, so this sounds like a bug to me.

> no way to define a schema on boot
> ---------------------------------
>
>                 Key: CASSANDRA-1021
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1021
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jeff Hodges
>            Assignee: Gary Dusbabek
>
> As of the latest in trunk, we are unable to define a schema to be created on boot. Having
to send an RPC to a new node as it joins the cluster means  we are unable to "boot and forget"
a new machine to have it all Just Work. It also might cause some weirdness between boot and
schema update (or did I miss something?).  
> At the cassandra hackathon, Stu had the good idea of copying over the definitions keyspace,
but, of course, this is less ideal than Just Working. Is there a way to make the on-first-boot
schema definition possible alongside the new dynamism of the runtime schema changes?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message