@busbey busbey released this Aug 15, 2018

Assets 32

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

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
  • 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.