YCSB/cassandra
Kevin Risden 393c611879 [version] update master to 0.8.0-SNAPSHOT. 2016-02-16 07:34:02 -06:00
..
src/main/java/com/yahoo/ycsb/db [core, Cassandra, gemfire, mapkeeper] Fixing squid:S2864 - "entrySet()" should be iterated when both the key and value are needed 2016-01-02 10:16:21 +05:00
README.md [cassandra] added large deprecation message 2015-12-17 09:24:29 -06:00
pom.xml [version] update master to 0.8.0-SNAPSHOT. 2016-02-16 07:34:02 -06:00

README.md

THIS BINDING IS DEPRECATED


Date of removal from YCSB: March 2016

Due to the low amount of use and support for older Cassandra lineages (0.X and 1.X), YCSB will not support clients for these versions either.

For Cassandra 2.X use the cassandra2-cql client: https://github.com/brianfrankcooper/YCSB/tree/master/cassandra2.

Cassandra (0.7, 0.8, 1.x) drivers for YCSB

For Cassandra 2 CQL support, use the cassandra2-cql binding. The Thrift drivers below are deprecated, and the CQL driver here does not support Cassandra 2.1+.

There are three drivers in the Cassandra binding:

  • cassandra-7: Cassandra 0.7 Thrift binding.
  • cassandra-8: Cassandra 0.8 Thrift binding.
  • cassandra-10: Cassandra 1.0+ Thrift binding.
  • cassandra-cql: Cassandra CQL binding, for Cassandra 1.x to 2.0. See cassandra2/README.md for details on parameters.

cassandra-10

Creating a table

Using cassandra-cli:

  create keyspace usertable with placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy' and strategy_options = {replication_factor:1};

  create column family data with column_type = 'Standard' and comparator = 'UTF8Type';

Note that replication_factor and consistency levels (below) will affect performance.

Configuration Parameters

  • hosts (required)
    • Cassandra nodes to connect to.
    • No default.
  • port
    • Thrift port for communicating with Cassandra cluster.
    • Default is 9160.
  • cassandra.readconsistencylevel

  • cassandra.scanconsistencylevel

  • cassandra.writeconsistencylevel

    • Default value is ONE
    • Consistency level for reads and writes, respectively. See the DataStax documentation for details.
    • Note that the default setting does not provide durability in the face of node failure. Changing this setting will affect observed performance. See also replication_factor, above.