Adding ConsistencyLevel to CassandraCqlState to fix #22
[maven-release-plugin] prepare release storm-cassandra-cql-0.1.9
[maven-release-plugin] prepare for next development iteration
Merge branch 'master' of github.com:hmsonline/storm-cassandra-cql
Explicit consistency levels for batches, conditional updates, and cluster CQL connections.

INTENTIONALLY BREAKING BACKWARDS COMPATIBILITY

Should release as 0.2
Merge pull request #26 from boneill42/master

Explicit consistency levels for batches, cluster, and conditional updates.
Add 0.2.0 CHANGELOG
[maven-release-plugin] prepare release storm-cassandra-cql-0.2.0
[maven-release-plugin] prepare for next development iteration
Updating to QUORUM as default (and in tests)
Kudos to @bflad, he was right.
Don't try to run LOCAL_QUORUM against a single node. =)
Merge branch 'boneill42-master'
Add CHANGELOG for 0.2.1
[maven-release-plugin] prepare release storm-cassandra-cql-0.2.1
[maven-release-plugin] prepare for next development iteration
Changing the way we default consistency level in the constructor.
Merge pull request #28 from boneill42/master

Changing the way we default consistency level in the constructor.
Adding reconnect incase the cluster gets closed.
(which is possible since it is a static variable -- other thread may have somehow closed it)
Adding warn message if need to reconstruct cluster because of close.
Merge pull request #29 from boneill42/master

	Adding reconnect incase the cluster gets closed