You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Johan Oskarsson (JIRA)" <ji...@apache.org> on 2010/04/19 13:00:55 UTC
[jira] Created: (CASSANDRA-1001) Improve messaging and reduce
barrier to entry post CASSANDRA-44
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
Reporter: Johan Oskarsson
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.
[jira] Commented: (CASSANDRA-1001) Improve messaging and reduce
barrier to entry post CASSANDRA-44
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890871#action_12890871 ]
Jonathan Ellis commented on CASSANDRA-1001:
-------------------------------------------
that's more germane to 1237 than here
> 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 beta 1
> Reporter: Johan Oskarsson
> Assignee: Jon Hermes
> Fix For: 0.7 beta 1
>
>
> 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.
[jira] Commented: (CASSANDRA-1001) Improve messaging and reduce
barrier to entry post CASSANDRA-44
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890855#action_12890855 ]
Stu Hood commented on CASSANDRA-1001:
-------------------------------------
> let's expose StorageService.loadSchemaFromYAML in nodetool and call this good
Also, naming it something that implies an upgrade would be helpful: CASSANDRA-1237 would like to hook into this upgrade process, and it isn't really Yaml related.
> 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 beta 1
> Reporter: Johan Oskarsson
> Assignee: Jon Hermes
> Fix For: 0.7 beta 1
>
>
> 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.
[jira] Assigned: (CASSANDRA-1001) Improve messaging and reduce
barrier to entry post CASSANDRA-44
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-1001:
-----------------------------------------
Assignee: Jon Hermes (was: Johan Oskarsson)
let's expose StorageService.loadSchemaFromYAML in nodetool and call this good
> 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
> Assignee: Jon Hermes
> 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.
[jira] Assigned: (CASSANDRA-1001) Improve messaging and reduce
barrier to entry post CASSANDRA-44
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-1001:
-----------------------------------------
Assignee: Johan Oskarsson
> 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
> Assignee: 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.
[jira] Commented: (CASSANDRA-1001) Improve messaging and reduce
barrier to entry post CASSANDRA-44
Posted by "Sylvain Lebresne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858469#action_12858469 ]
Sylvain Lebresne commented on CASSANDRA-1001:
---------------------------------------------
I do agree and I wonder, as commented by Ryan King on [CASSANDRA-957|https://issues.apache.org/jira/browse/CASSANDRA-957],
wouldn't [CASSANDRA-526|https://issues.apache.org/jira/browse/CASSANDRA-526] be the way to go ? That way we could load schema,
start the bootstrap and more on brand new nodes.
> 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
> Reporter: Johan Oskarsson
>
> 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.
[jira] Commented: (CASSANDRA-1001) Improve messaging and reduce
barrier to entry post CASSANDRA-44
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CASSANDRA-1001) Improve messaging and reduce
barrier to entry post CASSANDRA-44
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1001:
--------------------------------------
Fix Version/s: 0.7
Affects Version/s: 0.7
> 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.
[jira] Commented: (CASSANDRA-1001) Improve messaging and reduce
barrier to entry post CASSANDRA-44
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858519#action_12858519 ]
Jonathan Ellis commented on CASSANDRA-1001:
-------------------------------------------
I'm not sure that we need more than a better Upgrading section in NEWS. loadFromXML is pretty dirt simple. Of course you are welcome to add it to nodetool if "digging around for some obscure loading method" is too hard.
> 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.
[jira] Resolved: (CASSANDRA-1001) Improve messaging and reduce
barrier to entry post CASSANDRA-44
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-1001.
---------------------------------------
Assignee: (was: Jon Hermes)
Resolution: Duplicate
Jon points out there is already a patch for this in CASSANDRA-1133
> 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 beta 1
> Reporter: Johan Oskarsson
> Fix For: 0.7 beta 1
>
>
> 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.