Differences between revisions 45 and 46
Revision 45 as of 2013-11-13 18:21:59
Size: 4059
Comment: start nudging people to cqlsh
Revision 46 as of 2016-08-15 16:01:21
Size: 809
Comment: link cqlsh docs
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
The Cassandra CLI is a holdover from the pre-CQL Thrift [[API]]. You should migrate to [[http://www.datastax.com/documentation/cql/3.1/webhelp/index.html#cql/cql_reference/about_cql_ref_c.html|cqlsh]], which supports everything you could do from the CLI. How does your Thrift data map to CQL? See these three articles: The Cassandra CLI is a holdover from the pre-CQL Thrift API. You should migrate to cqlsh, which supports everything you could do from the CLI.

[[http://cassandra.apache.org/doc/latest/tools/cqlsh.html|cqlsh documentation is here]].

Uprading and wondering how your Thrift data maps to CQL? See these three articles:
Line 8: Line 12:
The CLI will be formally deprecated starting with Cassandra 2.1 and removed in 3.0. The CLI was formally deprecated starting with Cassandra 2.1 and removed in 3.0.
Line 10: Line 14:
== Older versions of the CLI ==

The examples below have been tested with Cassandra 1.0.6. For instructions for previous versions of Cassandra see one of: CassandraCli07, CassandraCli06.

You may also be interested in the [[http://www.datastax.com/docs/1.0/dml/using_cli|DataStax documentation]] which has excellent coverage on this topic.

== Starting the CLI ==
You can start the CLI using the {{{bin/cassandra-cli}}} script in your Cassandra installation ({{{bin\cassandra-cli.bat}}} on windows). If you are evaluating a local cassandra node then be sure that it has been correctly configured and successfully started before starting the CLI.

If successful you will see output similar to this:

{{{
Welcome to cassandra CLI.

Type 'help;' or '?' for help. Type 'quit;' or 'exit;' to quit.
}}}
You must then specify a system to connect to:

{{{
connect localhost/9160;
}}}
== Creating a Keyspace ==
We first create a keyspace to run our examples in.

{{{
create keyspace Twissandra;
}}}
== Selecting the keyspace to user ==
We must then select our example keyspace as our new context before we can run any queries.

{{{
use Twissandra;
}}}
== To Create A Column ==
We can then create a column to play with.

{{{
create column family User with comparator = UTF8Type;
}}}
For the later examples to work you must also update the schema using the following command. This will set the return type for the first and last name to make them human readable. It will also add and index for the age field so that you filter your gets using the Users name field.

{{{
update column family User with
        column_metadata =
        [
        {column_name: first, validation_class: UTF8Type},
        {column_name: last, validation_class: UTF8Type},
        {column_name: age, validation_class: UTF8Type, index_type: KEYS}
        ];
}}}
== To Add Data ==
To add data we want to into our new column we must first specify our default key type otherwise we would have to specify it for each key using the format {{{[utf8('keyname')]}}} this is probably advisable if you have mixed key types but makes simple cases harder to read.

So we run the command below, which will last the length of you cli session. On quitting and restarting we must run it again.

{{{
assume User keys as utf8;
}}}
and then we add our data.

{{{
set User['jsmith']['first'] = 'John';
set User['jsmith']['last'] = 'Smith';
set User['jsmith']['age'] = '38';
}}}
If you get the error like this {{{cannot parse 'John' as hex bytes}}}, then it likely you either haven't set your default key type or you haven't updated your schema as in the create column example.

''' The set command uses [[API#insert]]'''

== To Update Data ==
If we need to update a value we simply set it again.

{{{
set User['jsmith']['first'] = 'Jack';
}}}
== To Get Data ==
Now let's read back the `jsmith` row to see what it contains:

{{{
get User['jsmith'];
}}}
''' The get command uses [[API#get_slice]]'''

== To Query Data ==
{{{
get User where age = '12';
}}}
== For help ==
{{{
help;
}}}
== To Quit ==
{{{
quit;
}}}
== To Execute Script ==
{{{
bin/cassandra-cli -host localhost -port 9160 -f script.txt
}}}

Use cqlsh Instead

The Cassandra CLI is a holdover from the pre-CQL Thrift API. You should migrate to cqlsh, which supports everything you could do from the CLI.

cqlsh documentation is here.

Uprading and wondering how your Thrift data maps to CQL? See these three articles:

The CLI was formally deprecated starting with Cassandra 2.1 and removed in 3.0.

stats

CassandraCli (last edited 2016-08-15 16:01:21 by JonathanEllis)