Yahoo! Cloud Serving Benchmark
Downstream users should note that these release notes cover some changes already included in the 0.16.0 non-production release.
site.ycsb and Java packages have changed to be in site.ycsb (#1340)hbase098, hbase10, hbase12, hbase14, and asynchbase bindings and CDH6 via hbase20 binding
ignite and ignite-sql)
cassandra-cql binding with SSL (#1294)postgrenosql binding (#1242)voltdb binding (#1319)accumulo1.7 and accumulo1.8)cassandra-cql)geode)kudu)arangodb)azuretablestorage binding).couchbase2 binding).dynamodb binding).foundationdb)googledatastore)maprdb and maprjsondb)riak binding).redis)rest binding).rocksdb)tarantool binding).cassandra-cql)If you make use of one of these stores and can verify it works, please add a note to #1355
site.ycsb (#1340)site.ycsb (#1340)UPPERCASE WARNING: THIS IS A RELEASE CANDIDATE AND IS NOT INTENDED FOR DOWNSTREAM USE.
This source is a candidate for release 0.17.0. Please see #1355 issue for changes since 0.15.0, testing instructions, and where to leave your feedback.
Note on non-production status: due to available testing time from our volunteers, core and datastore changes for this release did not meet our usual bar for release testing. As a result, we've decided to publish this release as-is and put effort towards reestablishing testing for the next release cycle. Users interested in making use of this release are advised to check on issue #1265 for any status updates. If you get to test out one of the bindings changed in this release, please leave a note on that issue so that the work isn't repeated.
UPPERCASE WARNING: THIS IS A RELEASE CANDIDATE AND IS NOT INTENDED FOR DOWNSTREAM USE.
This source is a candidate for release 0.16.0. Please see #1265 issue for changes since 0.15.0, testing instructions, and where to leave your feedback.
accumulo1.7 and accumulo1.8)
arangodb)
arangodb binding should now work with versions 2.7-3.3. The arangodb3 binding is deprecated. (#1166)foundationdb)ignite and ignite-sql)rocksdb)aerospike)asynchbase binding).googlebigtable binding).hbase10 binding)cassandra-cql)couchbase2 binding).googledatastore)dynamodb binding).geode)hbase10, hbase12, hbase14, and hbase20)kudu)maprdb and maprjsondb)mongodb and mongodb-async)orientdb binding).riak binding).redis)rest binding).azuretablestorage binding).tarantool binding).s3)cassandra-cql)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.
UPPERCASE WARNING: THIS IS A RELEASE CANDIDATE AND IS NOT INTENDED FOR DOWNSTREAM USE.
This source is a candidate for release 01.5.0. Please see #1204 issue for testing instructions and where to leave your feedback.
Compared to the previous release, this candidate includes
Downstream users should note that these release notes cover some changes already included in the 0.13.0 non-production release.
int primitive type to long as a step towards providing greater key ranges. If you've implemented your own generator, measurements, or db binding this change will likely impact you. (see #911)TEXT instead of VARCHAR. The Table setup utility has been updated to reflect this.accumulo1.8)aerospike)
cassandra-cql)
googledatastore)
geode)
hbase10, hbase12, hbase14, and hbase20)
kudu)
maprdb and maprjsondb)mongodb and mongodb-async)
redis)
s3)
cassandra-cql)asynchbase binding).googlebigtable binding).hbase10 binding)couchbase2 binding).dynamodb binding).orientdb binding).rest binding).riak binding).azuretablestorage binding).tarantool binding).The built-in no-op binding basicdb has added a property basicdb.count. When set to true, we'll count operations that happen. Defaults to false. (see #1005)
The core of YCSB now contains a new base workload type to enable building timeseries based workloads. The current state is in flux and should be considered experimental by folks who would like to build on it. For details on work to date, see #1008, #1091, #1095. Interested parties are encouraged to check in on PR #1068 for ongoing work.
Special thanks for helping to test this release goes out to: @twblamer, @robertpang, @metatype, @upthewaterspout, @fwang29, @haih-g, @bosher, @ctubbsii , @rohanjayaraj, @isuntsov-gridgain, @petersomogyi, @jojochuang
UPPERCASE WARNING: THIS IS A RELEASE CANDIDATE AND IS NOT INTENDED FOR DOWNSTREAM USE.
This source is a candidate for release 0.14.0. Please see #1117 issue for a list of changes since the 0.12.0 release, testing instructions, and where to leave your feedback.
Note on non-production status: due to available testing time from our volunteers, core and datastore changes for this release did not meet our usual bar for release testing. As a result, we've decided to publish this release as-is and put effort towards reestablishing testing for the next release cycle. Users interested in making use of this release are advised to check on issue #981 for any status updates. If you get to test out one of the bindings changed in this release, please leave a note on that issue so that the work isn't repeated.
int primitive type to long as a step towards providing greater key ranges. If you've implemented your own generator, measurements, or db binding this change will likely impact you. (see #911)TEXT instead of VARCHAR. The Table setup utility has been updated to reflect this.ycsb.sh and ycsb.bat, don't work from a source checkout. Work around by using the python script ycsb (see #877)basicdb.count mode to track counts of operations (see #1005)Thanks to all the contributors that pushed on this release: @manolama, @twblamer.
UPPERCASE WARNING: THIS IS A RELEASE CANDIDATE AND IS NOT INTENDED FOR DOWNSTREAM USE.
This source is the first release candidate for version 0.13.0. The associated issue #981:
provides the list of changes since version 0.12.0 contains testing instructions is the recommended location for leaving any feedback