This commit removes an unrelated POM change for the original
(Elasticsearch 2) binding.

This commit wraps the usage of a content builder in a try-with-resources
block to ensure that it is correctly closed.

This commit changes the name of a property, es.newdb, to es.new_index as
this is more consistent with the terminology used in Elasticsearch.

This commit removes some unnecessary logging statements for the
elasticsearch5 and elasticsearch5-rest bindings.

This commit sets the log of the internal transport client used in the
Elasitcsearch 5 binding to use standard error instead of standard out.

This commit reverts some unrelated changes to POMs for other bindings,
perhaps made inadvertently while merging master into a development
branch.

This commit adds some basic formatting to the transport client logs for
the transport client used in the Elasticsearch 5 binding.

This commit sets the Elasticsearch 5 binding to only use the
elasticsearch-maven-plugin if tests are running on JDK 8.

This commit updates the Elasticsearch 5 binding docs to include
references for starting Elasticsearch 5, how to configure the transport
client, and how to use the low-level REST client binding.

This commit fixes issues with the Elasticsearch 5 transport client and
REST client bindings so that all tests pass.

This commit is a straightforward code cleanup of the Elasticsearch 5
transport client and REST client implementations.

This commit is an initial cut at a complete implementation using the
low-level Elasticsearch REST client.

This commit fixes a bug in the Elasticsearch 5 transport client
binding. Namely, the update method was not indexing using the ID of the
read document, but instead the provided key. As auto-generated IDs are
used, this is a mistake as this is not the ID of the document. This
commit fixes this issue.

Additionally, the type is passed to the search method and used in
searches. While this is not a correctness issue per se, we fix it for
clarity.

We can remove the path.home setting for the Elasticsearch 5 binding for
the transport client so this commit does that.

This commit refactors the indexing of documents in the Elasticsearch 5
binding to use auto-generated IDs, instead indexing the key field as a
dedicated field rather than using it as the ID. This enables us to
implement scan functionality which we add in this commit as well.

Upstream Elasticsearch does not support embedded nodes as of
Elasticsearch 5. This commit removes the usage of embedded nodes within
YCSB.

Since Elasticsearch 5, Elasticsearch is now strict about settings. This
means that if you pass it a setting that it does not recognize,
Elasticsearch will throw an exception whereas previously it was lenient
in such situations. This commit removes passing all properties as
settings to Elasticsearch in favor of a special prefix es.setting for
which properties prefixed with this will be passed as settings to
Elasticsearch.

If path.home is not set we should not add it to the settings object used
to construct the transport client otherwise we will hit a null pointer
exception due to the null value being dereferenced in the internals of
Elasticsearch.

This commit bumps the Elasticsearch dependency version of the
Elasticsearch 5 binding to version 5.5.1.

* master:
  [core] Fixing squid:S1319 -  Declarations should use Java collection interfaces such as "List" rather than specific implementation classes such as "LinkedList". (manolama - updated bindings added since the PR)
  [core] Use longs instead of ints to support larger key spaces. Changed int to long in Measurements code to support large scale workloads. (manolama - fixed checkstyle errors)
  [core] Export totalHistogram for HdrHistogram measurement
  [core] Add an operation enum to the Workload class. This can eventually be used to replace the strings.
  [core] Add a Fisher-Yates array shuffle to the Utils class.
  [core] Fix an issue where the threadid and threadCount were not passed to the workload client threads. Had to use setters to get around the checkstyle complaint of having too many parameters.
  Upgrading googlebigtable to the latest version. The API used by googlebigtable has had quite a bit of churn.  This is the minimal set of changes required for the upgrade.
  [geode] Update to apache-geode 1.2.0 release
  [core] Update to use newer version of Google Cloud Spanner client and associated required change
  [core] Add a reset() method to the ByteIterator abstract and implementations for each of the children. This lets us re-use byte iterators if we need to access the values again (when applicable).
  [hbase12] Add HBase 1.2+ specific client that relies on the shaded client artifact provided by those versions. (#970)
  [distro] Refresh Apache licence text (#969)
  [memcached] support binary protocol (#965)
  [accumulo] A general "refresh" to the Accumulo binding (#947)
  [cloudspanner] Add binding for Google's Cloud Spanner. (#939)
  [aerospike] Change the write policy to REPLACE_ONLY (#937)

[core] Fixing squid:S1319 -  Declarations should use Java collection interfaces such as "List" rather than specific implementation classes such as "LinkedList".
(manolama - updated bindings added since the PR)

Signed-off-by: Chris Larsen <clarsen@yahoo-inc.com>

Changed int to long in Measurements code to support large scale workloads.
(manolama - fixed checkstyle errors)

Signed-off-by: Chris Larsen <clarsen@yahoo-inc.com>

Signed-off-by: Chris Larsen <clarsen@yahoo-inc.com>

be used to replace the strings.

to the workload client threads. Had to use setters to get around the
checkstyle complaint of having too many parameters.

[core] Add a reset() method to the ByteIterator abstract and implemen…

The API used by googlebigtable has had quite a bit of churn.  This is the minimal set of changes required for the upgrade.

Signed-off-by: Chris Larsen <clarsen@yahoo-inc.com>

Also fix a read serialization issue with client mode driver.

Signed-off-by: Chris Larsen <clarsen@yahoo-inc.com>

Signed-off-by: Chris Larsen <clarsen@yahoo-inc.com>

for each of the children. This lets us re-use byte iterators if we need to
access the values again (when applicable).

[hbase12] Add HBase 1.2+ specific client that relies on the shaded client artifact provided by those versions. (#970)

Closes #967

Adding support for memcached binary protocol as described in
https://github.com/memcached/memcached/blob/master/doc/protocol.txt.

Protocol can be set via memcached.protocol property of YCSB memcached workload. if specified
protocol must be "binary" or "text". If unspecified text version is used.

* Expand on the README, covering table creation and best-practices for table config
* Avoid unnecessary Text object creations (in loops and instead of byte[] usage)
* Use a ConcurrentHashMap to better match the DB API
* Fix error messages and always call printStackTrace() on exceptions
* Use BATCHED_OK instead of OK in insert() (more correct)

The original Aerospike interface layer was created when the REPLACE_ONLY option was not available.  This provides a policy more in line with the policies that other databases have implemented their interface layers.