YCSB 0.15.0

Known Issues

• The mongodb binding does not honor the maxPoolSize=XX parameter and instead opens a connection per client thread. (see #317)
• Datastore drivers that lack timeouts may result in YCSB failing to honor the maxexecutiontime parameter. (see #618)
• "Latest" distribution does not work properly on update transactions. (see #640)
• Accumulo client currently always claims success even when the record it's supposed to operate on (e.g. for a read) doesn't exist. (see #699)
• JDK 9 and JDK 10 are not supported. (see #704)
• ArangoDB client bindings fail to work with ArangoDB authentication (see #1155)
• HBase 2.0 client bindings doesn't include an slf4j logging-binding and so doesn't provide log messages from the client library (see #1173)
• The Accumulo client bindings do not work with kerberos enabled clusters (see #1211)

Tested Datastores

New or changed, tested and verified to work in this release

• Apache Accumulo 1.9.2 and 1.7.2-cdh5.5.0 (via accumulo1.7 and accumulo1.8)
  • client version bump (#1167)
• ArangoDB 3.3 and 3.4 (nightly) (via arangodb)
  • The arangodb binding should now work with versions 2.7-3.3. The arangodb3 binding is deprecated. (#1166)
• 🆕 FoundationDB 5.2.5 (via foundationdb)
• 🆕 Apache Ignite (incubating) 2.6.0 (via ignite and ignite-sql)
• 🆕 RocksDB (via rocksdb)

Tested in previous releases, unchanged in this release

• Aerospike 4.2.0.3 (via aerospike)
• AsyncHBase 1.7 (via asynchbase binding).
• Google Bigtable (via googlebigtable binding).
• Google Bigtable accessing using the HBase client (via hbase10 binding)
• Apache Cassandra 3.11.2 (via cassandra-cql)
• Couchbase2 4.0 and 4.5 (via couchbase2 binding).
• Google Cloud Datastore (via googledatastore)
• DynamoDB using AWS SDK 1.10.48 (via dynamodb binding).
• Apache Geode 1.2.0, 1.3.0, and 1.6.0 (via geode)
• Apache HBase 1.2 (CDH 5.14.2) and 2.0 (CDH 6.0.0-beta1) (via hbase10, hbase12, hbase14, and hbase20)
• Apache Kudu 1.8.0 (via kudu)
• MapR 6.0.1 (via maprdb and maprjsondb)
• MongoDB 3.6.4 (via mongodb and mongodb-async)
• OrientDB 2.2.10 (via orientdb binding).
• Riak 2.x.y (via riak binding).
• Redis 4.0.9 in non-cluster mode (via redis)
• REST (via rest binding).
• Azure Table Storage (via azuretablestorage binding).
• Tarantool 1.6.6-249, 1.6.8, 1.7-alpha (via tarantool binding).
• Amazon S3 (via s3)
• YugaByte DB 1.0.0 (via cassandra-cql)

Untested Datastores

• Apache Accumulo versions prior to 1.7
• Apache Cassandra versions prior to 3
• Couchbase versions prior to 4
• Google Cloud Bigtable
• Google Cloud Spanner
• Azure DocumentDB
• Elastic Search
• HyperTable
• Infinispan
• JDBC
• Mapkeeper
• Memcached
• MongoDB versions prior to 3.6
• NoSQLDB
• Rados
• Redis versions prior to 4
• Redis in cluster mode
• Apache Solr 5 and 6

Framework Changes

field and scan length minimums are now configurable

When using a field length that has a non-constant distribution (i.e. uniform or zipfian) via the fieldlengthdistribution property, you can now specify a minimum length by setting the property minfieldlength. It defaults to a value of 1 and must be set to something less than or equal to the fieldlength property.

When running a workload with SCAN operations, you can now specify a minimum length for the scan by setting the property minscanlength. It defaults to a value of 1 and must be set to something less than or equal to the maxscanlength property.

For more information see #1177.