- define checkstyle configs in as few places as possible
- use checkstyle:check since it has defaults that match what we want (fail after logging to console)
- modules that have current failures set property checkstyle.failOnViolation to false.
updating readme
updating package info
perfecting logic for http solr clients for all operations
renamed properties, tested cloud mode and cleaned code
removed dependency on dynamic field names, updated readme
now enforcing checkstyle
adding solr artifact
removing test cases relying on external dependencies
removed unused maven dependencies, added batch mode support, all try blocks now catch eplicit exceptions, Query/UpdateResponse status codes are handled more granularly, updated readme, added sample schema.xml file to support default field names in ycsb client, updated all license headers to 2016, using SolrClient object as primary client type regardless if Solr is running in Cloud or Stand-alone mode
cleaned code and config files, now accepting a solr base url property, simplified sample schema.xml file, renamed class to SolrClient, now updating documents atomically, added batch support to delete method
updated new line spacing of pom file comments
removed sample schema file, updated readme with more indepth explanation on running/setting up the solr-binding
removed some code lines no longer in use
renamed zookeeper param name, now throwing caught exceptions where appropriate, debug messages are now being logged on stderr
now returning an appropriate error if we receive an unexpected response from solr server, repeated calls to getResults is no longer
now using singletonMap to store update params in, fixed typo and missing id field in sample config in README
The memcached support was extracted from PR #98 by @jbellis, with cleanups to
bring it in line with current APIs and style guide.
This PR also addresses issue #326.
Add a DB client for Google Cloud Datastore. This initial commit includes implementation of all CRUD operations (modulo scan), and integration into the rest of YCSB (pom.xml changes, etc)
Next few commits will include Scan/query support, single entity group support, and better documentation.
* remove unused declared deps in a few places
* lex sort modules in top level pom
* update maven plugin versions.
* no more jar-with-dependencies
* set ycsb-core to provided in bindings
* introduce a bindings-parent pom that sets
** stage dependency copy on building binding
** iff binding has a README.md, build a binding-specific dist artifact
* update distribution assembly to
** properly build after modules
** use per-binding sets of dependencies
closes#250
http://tarantool.org and https://github.com/tarantool/tarantool
In "mail.ru" we wrote and widely use Tarantool key-value database.
It's key properties include:
* Defferent index types with iterators:
- HASH (the fastest)
- TREE (range and ordered retreival)
- BITSET (bit mask search)
- RTREE (geo search)
* multipart keys for HASH and TREE indexes
* Data persistence with by Write Ahead Log (WAL) and snapshots.
* asynchronous master-master replication, hot standby.
* coroutines and async. IO are used to implement high-performance lock-free access to data.
- socket-io/file-io with yeilds from lua
* stored procedures in Lua (Using LuaJIT)
* supports plugins written on C/C++ (Have two basic plugins for working with MySQL and PostgreSQL)
* Authentication and access control
Move 'distribution target' to the end (it's needed for .jar to be in the .tar.gz)
* enabling gemfire module and updating to release 7.0.2
* verified that there are no failures while trying to resolve gemfire repo.
* fixed an NPE.
Amending-Author: Sean Busbey <sean.busbey@gmail.com>
Signed-off-by: Sean Busbey <sean.busbey@gmail.com>
* Need a SNAPSHOT version because non-SNAPSHOT is reserved for actual releases.
* Increment minor version per pre-1.0 guidelines from the Version Numbers guide
Fixes#236.