Uploaded image for project: 'Apache Cassandra'
  1. Apache Cassandra
  2. CASSANDRA-3933

./bin/cqlsh `describe keyspace <keyspace>` command doesn't work when ColumnFamily row_cache_provider wasn't specified.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Low
    • Resolution: Fixed
    • 1.0.8
    • None
    • Low

    Description

      I have created Keyspace and ColumnFamily using CLI

      /bin/cassandra-cli --host localhost
      Connected to: "Test Cluster" on localhost/9160
      Welcome to Cassandra CLI version 1.0.7-SNAPSHOT
      
      Type 'help;' or '?' for help.
      Type 'quit;' or 'exit;' to quit.
      
      [default@unknown] create keyspace ks;
      f89384f0-5bd3-11e1-0000-242d50cf1fff
      Waiting for schema agreement...
      ... schemas agree across the cluster
      [default@unknown] use ks;
      Authenticated to keyspace: ks
      [default@ks] create column family cf;
      fc807690-5bd3-11e1-0000-242d50cf1fff
      Waiting for schema agreement...
      ... schemas agree across the cluster
      [default@ks] quit;
      

      and then I have tried to describe keyspace using CQLsh

      ./bin/cqlsh                     
      Connected to Test Cluster at localhost:9160.
      [cqlsh 2.0.0 | Cassandra 1.0.7-SNAPSHOT | CQL spec 2.0.0 | Thrift protocol 19.20.0]
      Use HELP for help.
      cqlsh> describe keyspace ks;
      
      CREATE KEYSPACE ks WITH strategy_class = 'NetworkTopologyStrategy'
        AND strategy_options:datacenter1 = '1';
      
      USE ks;
      
      CREATE COLUMNFAMILY cf (
      CfDef instance has no attribute 'row_cache_provider'
        KEY blob PRIMARY KEYcqlsh> 
      

      Attachments

        Activity

          People

            thepaul paul cannon
            xedin Pavel Yaskevich
            paul cannon
            Sylvain Lebresne
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: