* [scylla] token awareness is enabled by default
See
https://docs.datastax.com/en/developer/java-driver/3.10/manual/load_balancing/ :
> If you don’t explicitly configure the policy,
> you get the default, which is a datacenter-aware,
> token-aware policy.
* [scylla] driver: update to 3.10.2-scylla-1
* [scylla] log used consistency level
* [scylla] doc: add latency correction section
* [scylla] doc: dump and merge histograms
* [scylla] doc: don't configure connections manually
https://github.com/scylladb/java-driver/commits/3.10.2-scylla
* [scylla] doc: details to sections 1,2,4,5
* updated to latest recommended java sdk
* cleaned up binding implementation based on latest sdk
* added a default user agent string of 'azurecosmos-ycsb'
Co-authored-by: Andrew Feldman <Andrew.Feldman@microsoft.com>
* Upgrade AWS SDK from version 1.10.48 to 1.11.812.
* Introduce a new configuration parameter, dynamodb.region, which
represents a valid AWS region code (see
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-available-regions
for example). If specifying the region, it is not necessary to specify
the dynamodb.endpoint parameter.
* Introduce support for non-standard endpoints. Before this commit,
setting the endpoint to a non-standard one, like a proxy, but
ultimately connecting to a region different from 'us-east-1' would
lead to a credential errors due to bad signature:
ERROR site.ycsb.db.DynamoDBClient
-com.amazonaws.AmazonServiceException: Credential should be scoped to
a valid region, not 'us-east-1'. (Service: AmazonDynamoDBv2; Status
Code: 400; Error Code: InvalidSignatureException;
With this commit, if using a proxy as an endpoint, by setting also the
region via dynamodb.region, it will work with no error.
* Set TCP Keep-Alive to true. Even it makes sense to be used by YCSB, it
apparently doesn't improve performance notably given the connection
reuse that the DynamoDB client is doing.
* Update the example config file with the endpoint and region parameters
and behavior.
Some clients may be more efficient when you pass in the column name,
instead of forcing the client to do a wildcard scan. This is the case
with googlebigtable, when there is only 1-3 columns.
This fixes a security vulnerability in this project where the `pom.xml`
files were configuring Maven to resolve dependencies over HTTP instead of
HTTPS.
Alters dependency resolution for
* cassandra
* hypertable
* maprdb
* maprjsondb
* mongodb
closes#1406
* remove 0.98, 1.0, 1.2, and 2.0 bindings
* change the 1.4 binding to be a "HBase 1.y" binding
* add "HBase 2.y" binding and default it to the current 2.2 release
* incorporate README from 0.98 binding into current bindings
* incorporate README on bigtable testing from 1.0 binding into 1.4 binding
* incorporate implementation from 1.0 client into current bindings
* updated asynchbase binding to include parts of removed bindings it referenced
* update maprdb binding for the change in the hbase bindings
* update 1.4 and 2.2 to current releases
* use shaded client test for all hbase bindings.
* make hbase bindings consistently use log4j
* fixes#1173
* fixes#1172
Previously, if you defined maxexecutiontime and not defined operationcount
parameter (or set operationcount=0), then you were able to run YCSB for a
given period of time and measure the number of operations you get during
the load test.
Since #1323 was merged, it it not possible to use operationcount=0, as
the thread count will be set to 0 in this case and no client thread will
be created. This PR makes it possible to use operationcount=0 again.
fixes#1382
* changed the url splitting delimiter from , to ; to enable fail-over connection strings for JDBC
* included jdbc cluster connection strings in README
Co-authored-by: Sean Busbey <sean.busbey@gmail.com>
Microsoft Open Source
Ivan
Beata Sudi
maoling
Armaan Sood
Sean Busbey
Zhang Yifan
Rogério Pontes
Xing Lin
Chris Lu
Thiago Nunes
Álvaro Hernández
Justin Uang
Jonathan Leitschuh
naivewong
Harshavardhan Unnibhavi
Mubashir Kazia
Grant Henke
Kevin Risden
Asya Kamsky
Vishnu Bharathi
Mate Szalay-Beko
@FranckPachot
JulyChen728
twblamer
David Rolfe
seybi87
Kowsar Atazadeh