Return-Path: Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: (qmail 27570 invoked from network); 19 Apr 2010 14:39:15 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Apr 2010 14:39:15 -0000 Received: (qmail 29519 invoked by uid 500); 19 Apr 2010 14:39:14 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 29508 invoked by uid 500); 19 Apr 2010 14:39:14 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 29500 invoked by uid 99); 19 Apr 2010 14:39:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Apr 2010 14:39:14 +0000 X-ASF-Spam-Status: No, hits=-1310.6 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Apr 2010 14:39:14 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o3JEcr87021107 for ; Mon, 19 Apr 2010 10:38:54 -0400 (EDT) Message-ID: <25209333.11761271687933868.JavaMail.jira@thor> Date: Mon, 19 Apr 2010 10:38:53 -0400 (EDT) From: "Gary Dusbabek (JIRA)" To: commits@cassandra.apache.org Subject: [jira] Commented: (CASSANDRA-1001) Improve messaging and reduce barrier to entry post CASSANDRA-44 In-Reply-To: <2403042.8551271674855052.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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.