Go to file
Jacek Lewandowski d16e8d3653 Do not create sstable files before registering in txn
Refactoring prevents the situation where some sstable components, like
data or index, are created before the new sstable is registered with
lifecycle transaction, which leads to a problem such that there is
a short time when incomplete sstable components are present. At the same
time, no transaction file is created, which leads to the possibility
that the sstable can be recognized as completed by various
transaction-aware listers.

Patch by Jacek Lewandowski; reviewed by Branimir Lambov, Mike Adamson for CASSANDRA-18737
2023-09-25 18:47:56 +02:00
.build Merge branch 'cassandra-4.1' into cassandra-5.0 2023-09-25 12:39:39 +02:00
.circleci CircleCI: Fix BASE_BRANCH in generate.sh 2023-08-28 09:24:59 -04:00
.github Add pull request template and modify README to include Jira and mailing list link 2022-09-21 09:10:28 +02:00
.jenkins Merge branch 'cassandra-3.11' into cassandra-4.0 2023-08-31 22:39:56 +02:00
bin Merge branch 'cassandra-4.0' into cassandra-4.1 2023-09-05 16:53:45 +02:00
conf Fix accessing java.nio.Bits.TOTAL_CAPACITY in Java17 2023-09-14 12:00:11 -04:00
debian Merge branch 'cassandra-4.1' into cassandra-5.0 2023-09-19 20:34:03 +02:00
doc Remove metrics-reporter-config dependency 2023-09-12 10:14:59 -04:00
examples Merge branch 'cassandra-4.1' into trunk 2023-04-17 10:40:52 +02:00
ide Merge branch 'cassandra-4.0' into cassandra-4.1 2023-09-25 12:39:38 +02:00
lib remove pure_sasl from the repository 2022-09-02 15:21:52 +02:00
pylib Merge branch 'cassandra-4.1' into cassandra-5.0 2023-09-05 16:58:50 +02:00
redhat Fix rpm installation on jdk17 2023-09-04 16:59:27 +02:00
src Do not create sstable files before registering in txn 2023-09-25 18:47:56 +02:00
test Do not create sstable files before registering in txn 2023-09-25 18:47:56 +02:00
tools Remove legacy command line options from cassandra-stress 2023-08-09 23:16:36 +02:00
.asf.yaml Remove asf.yaml from non-trunk branches 2023-03-29 06:32:05 -05:00
.gitignore Ninja fix for CASSANDRA-18606 2023-09-05 17:20:36 +02:00
CASSANDRA-14092.txt Extend maximum expiration date 2023-06-05 07:18:34 +02:00
CHANGES.txt Do not create sstable files before registering in txn 2023-09-25 18:47:56 +02:00
CONTRIBUTING.md Merge branch 'cassandra-3.11' into trunk 2021-04-22 08:32:58 -05:00
LICENSE.txt Merge branch 'cassandra-3.11' into cassandra-4.0 2023-08-31 22:39:56 +02:00
NEWS.txt Remove metrics-reporter-config dependency 2023-09-12 10:14:59 -04:00
NOTICE.txt Merge branch 'cassandra-3.11' into cassandra-4.0 2023-02-22 10:25:08 -06:00
README.asc Move build and test scripts in-tree, under .build/ 2023-07-12 12:59:37 +02:00
TESTING.md Improve and clean up documentation and fix typos 2023-01-26 14:42:47 +01:00
build-shaded-dtest-jar.sh Merge branch 'cassandra-3.11' into trunk 2021-04-19 17:39:10 +02:00
build.properties.default Missing license info and headers 2023-08-31 22:30:42 +02:00
build.xml Merge branch 'cassandra-4.1' into cassandra-5.0 2023-09-25 12:39:39 +02:00
relocate-dependencies.pom Upgrade maven-shade-plugin to 3.4.1 to fix shaded dtest JAR build 2023-03-14 15:57:14 -05:00

README.asc

Apache Cassandra
-----------------

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

https://cwiki.apache.org/confluence/display/CASSANDRA2/Partitioners[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.

https://cwiki.apache.org/confluence/display/CASSANDRA2/DataModel[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 http://cassandra.apache.org/[the Apache Cassandra web site].

Issues should be reported on https://issues.apache.org/jira/projects/CASSANDRA/issues/[The Cassandra Jira].

Requirements
------------
- Java: see supported versions in build.xml (search for property "java.supported").
- Python: for `cqlsh`, see `bin/cqlsh` (search for function "is_supported_version").


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 https://cassandra.apache.org/doc/latest/cassandra/getting_started/index.html[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

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 6.2.0 | Cassandra 5.0-SNAPSHOT | CQL spec 3.4.7 | Native protocol v5]
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 KEYSPACE 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
http://cassandra.apache.org/doc/latest/cql/[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?

  * Join us in #cassandra on the https://s.apache.org/slack-invite[ASF Slack] and ask questions.
  * Subscribe to the Users mailing list by sending a mail to
    user-subscribe@cassandra.apache.org.
  * Subscribe to the Developer mailing list by sending a mail to
    dev-subscribe@cassandra.apache.org.
  * Visit the http://cassandra.apache.org/community/[community section] of the Cassandra website for more information on getting involved.
  * Visit the http://cassandra.apache.org/doc/latest/development/index.html[development section] of the Cassandra website for more information on how to contribute.