Cassandra
  1. Cassandra
  2. CASSANDRA-1001

Improve messaging and reduce barrier to entry post CASSANDRA-44

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Duplicate
    • Fix Version/s: 0.7 beta 1
    • Component/s: Core
    • Labels:
      None

      Description

      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.

        Activity

        Hide
        Jonathan Ellis added a comment -

        Jon points out there is already a patch for this in CASSANDRA-1133

        Show
        Jonathan Ellis added a comment - Jon points out there is already a patch for this in CASSANDRA-1133
        Hide
        Jonathan Ellis added a comment -

        that's more germane to 1237 than here

        Show
        Jonathan Ellis added a comment - that's more germane to 1237 than here
        Hide
        Stu Hood added a comment -

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

        Show
        Stu Hood added a comment - > 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.
        Hide
        Jonathan Ellis added a comment -

        let's expose StorageService.loadSchemaFromYAML in nodetool and call this good

        Show
        Jonathan Ellis added a comment - let's expose StorageService.loadSchemaFromYAML in nodetool and call this good
        Hide
        Jonathan Ellis added a comment -

        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.

        Show
        Jonathan Ellis added a comment - 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.
        Hide
        Gary Dusbabek added a comment -

        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.

        Show
        Gary Dusbabek added a comment - 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.
        Hide
        Sylvain Lebresne added a comment -

        I do agree and I wonder, as commented by Ryan King on CASSANDRA-957,
        wouldn't CASSANDRA-526 be the way to go ? That way we could load schema,
        start the bootstrap and more on brand new nodes.

        Show
        Sylvain Lebresne added a comment - I do agree and I wonder, as commented by Ryan King on CASSANDRA-957 , wouldn't CASSANDRA-526 be the way to go ? That way we could load schema, start the bootstrap and more on brand new nodes.

          People

          • Assignee:
            Unassigned
            Reporter:
            Johan Oskarsson
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development