cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1001) Improve messaging and reduce barrier to entry post CASSANDRA-44
Date Mon, 19 Apr 2010 14:38:53 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858506#action_12858506
] 

Gary Dusbabek commented on CASSANDRA-1001:
------------------------------------------

Whatever we choose, it needs to be explicit.  If it's not, there is no way to distinguish
from a node that a user wishes to load from xml from a a node that a user wishes to load from
gossip.

Post 0.7+1, one idea is to move the loadFromXML code and a snippet of XML into contrib and
supply some sort of tool that will load manually that way.

> Improve messaging and reduce barrier to entry post CASSANDRA-44
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-1001
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1001
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7
>            Reporter: Johan Oskarsson
>             Fix For: 0.7
>
>
> As seen on the mailinglist and from own experience the CASSANDRA-44 changes make it slightly
confusing for a first time user to get his first Cassandra instance up and running. We should
reduce the risk of turning away potential users.
> * Improve our messaging (README, error msg, NEWS etc). 
> * Make it much easier to load/create a schema after a first startup. Starting jconsole
and digging around for some obscure loading method is confusing and time consuming, we should
provide a simple tool to do so.

-- 
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