Skip to content
Mirror of Apache Cassandra
Branch: trunk
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Support building Cassandra with JDK 11 May 10, 2019
bin Merge branch 'cassandra-3.11' into trunk May 27, 2019
conf Introduce optional timeouts for idle client sessions Jul 10, 2019
debian Update log directory patch for 4.0 deb package Jun 26, 2019
doc Merge branch 'cassandra-3.11' into trunk Jul 15, 2019
examples/triggers Fix trigger example on 4.0 Aug 24, 2017
ide Merge branch 'cassandra-3.11' into trunk Apr 25, 2019
lib Update Netty dependencies to latest, clean up SocketFactory Jul 2, 2019
pylib Merge branch '14951-3.11' into 14951-trunk Jan 15, 2019
redhat Fix path to patches in RPM packaging Nov 13, 2018
src Merge branch 'cassandra-3.11' into trunk Jul 19, 2019
test Merge branch 'cassandra-3.11' into trunk Jul 19, 2019
tools Rewrite the internode messaging subsystem Jun 12, 2019
.gitignore Apache NetBeans project files Apr 11, 2019
.rat-excludes Remove Pig support Oct 16, 2015
CASSANDRA-14092.txt Merge branch 'cassandra-2.2' into cassandra-3.0 Feb 10, 2018
CHANGES.txt Merge branch 'cassandra-3.11' into trunk Jul 19, 2019
CONTRIBUTING.md Remove comment from CONTRIBUTING.md regarding closing GitHub PRs. Jan 9, 2019
LICENSE.txt merge with 0.6 branch (post-850) Mar 26, 2010
NEWS.txt Merge branch 'cassandra-3.11' into trunk Feb 19, 2019
NOTICE.txt Merge branch 'cassandra-3.11' into trunk Mar 8, 2019
README.asc Ninja: Update README with link to instructions for contributing Jun 15, 2017
TESTING.md Ninja trivial typo in TESTING Jun 21, 2018
build.properties.default Switch http to https URLs in build.xml May 22, 2019
build.xml Update Netty dependencies to latest, clean up SocketFactory Jul 2, 2019
eclipse_compiler.properties Add Static Analysis to warn on unsafe use of Autocloseable instances May 27, 2015

README.asc

Apache Cassandra

Apache Cassandra is a highly-scalable partitioned row store. Rows are organized into tables with a required primary key.

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster.

Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

For more information, see the Apache Cassandra web site.

Requirements

  1. Java >= 1.8 (OpenJDK and Oracle JVMS have been tested)

  2. Python 2.7 (for cqlsh)

Getting started

This short guide will walk you through getting a basic one node cluster up and running, and demonstrate some simple reads and writes. For a more-complete guide, please see the Apache Cassandra website’s Getting Started Guide.

First, we’ll unpack our archive:

$ tar -zxvf apache-cassandra-$VERSION.tar.gz
$ cd apache-cassandra-$VERSION

After that we start the server. Running the startup script with the -f argument will cause Cassandra to remain in the foreground and log to standard out; it can be stopped with ctrl-C.

$ bin/cassandra -f

Note for Windows users: to install Cassandra as a service, download Procrun, set the PRUNSRV environment variable to the full path of prunsrv (e.g., C:\procrun\prunsrv.exe), and run "bin\cassandra.bat install". Similarly, "uninstall" will remove the service.

Now let’s try to read and write some data using the Cassandra Query Language:

$ bin/cqlsh

The command line client is interactive so if everything worked you should be sitting in front of a prompt:

Connected to Test Cluster at localhost:9160.
[cqlsh 2.2.0 | Cassandra 1.2.0 | CQL spec 3.0.0 | Thrift protocol 19.35.0]
Use HELP for help.
cqlsh>

As the banner says, you can use 'help;' or '?' to see what CQL has to offer, and 'quit;' or 'exit;' when you’ve had enough fun. But lets try something slightly more interesting:

cqlsh> CREATE SCHEMA schema1
       WITH replication = { 'class' : 'SimpleStrategy', 'replication_factor' : 1 };
cqlsh> USE schema1;
cqlsh:Schema1> CREATE TABLE users (
                 user_id varchar PRIMARY KEY,
                 first varchar,
                 last varchar,
                 age int
               );
cqlsh:Schema1> INSERT INTO users (user_id, first, last, age)
               VALUES ('jsmith', 'John', 'Smith', 42);
cqlsh:Schema1> SELECT * FROM users;
 user_id | age | first | last
---------+-----+-------+-------
  jsmith |  42 |  john | smith
 cqlsh:Schema1>

If your session looks similar to what’s above, congrats, your single node cluster is operational!

For more on what commands are supported by CQL, see the CQL reference. A reasonable way to think of it is as, "SQL minus joins and subqueries, plus collections."

Wondering where to go from here?

You can’t perform that action at this time.