You can use both at once, but I also agree with the advice that you may want to stick to one. ;)
FWIW, we¹ve started work on storm-cassandra-cql: http://brianoneill.blogspot.com/2014/02/work-started-on-storm-cassandra-cql. html It isn¹t polished yet, but if you would like to standardize on CQL3 instead of straddling thrift and CQL, that might work for you. -brian --- Brian O'Neill Chief Technology Officer Health Market Science The Science of Better Results 2700 Horizon Drive King of Prussia, PA 19406 M: 215.588.6024 @boneill42 <http://www.twitter.com/boneill42> healthmarketscience.com This information transmitted in this email message is for the intended recipient only and may contain confidential and/or privileged material. If you received this email in error and are not the intended recipient, or the person responsible to deliver it to the intended recipient, please contact the sender at the email above and delete this email and any attachments and destroy any copies thereof. Any review, retransmission, dissemination, copying or other use of, or taking any action in reliance upon, this information by persons or entities other than the intended recipient is strictly prohibited. From: Adrian Mocanu <[email protected]> Reply-To: <[email protected]> Date: Tuesday, February 4, 2014 at 1:02 PM To: "[email protected]" <[email protected]> Subject: CQL3 and thrift Hi I have a quick question; I¹d like to know if it¹s ok to interchange CQL with Thrift (via Hector client) while inserting data into Cassandra version 2. My scenario is that I use CQL 3 to create keyspace and table and use CassandraState (which uses Hector client which is a Thrift client I believe). I¹ve heard all sorts of talk about sticking to only 1 instead of using both Thrift and CQL3 together. Can anyone comment if I can use both at once? Thanks -A
