Steve, You may want to cross post this over on the Cassandra list. Obviously, there should be nothing that you can do from a client-perspective that would render the contents of a CF unreadable.
What was the output in cqlsh when you tried to select from the table? The storm-cassandra implementation is a wrapper on top of Astyanax. You might also post there. You may need to enable debugging in storm-cassandra to see what calls are being made in order to get steps to reproduce. -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: "Gorman, Steve A." <[email protected]> Reply-To: <[email protected]> Date: Monday, February 10, 2014 at 4:01 PM To: "[email protected]" <[email protected]> Subject: Storm Cassandra and the CassandraCounterBatchingBolt All, I am getting an error using the CassandraCounterBatchingBolt complaining of an . invalid operation for non commutative column family LogVolumeByMinute I am following a tutorial from a book which is using Casandra to store text in a Column Family and auto-increment a counter column. I read that in order to use a counter column I had to have a default_validation_class of type CounterColumnType. So I created a CF like so create column family LogVolumeByMinute with default_validation_class=CounterColumnType and key_validation_class=UTF8Type and comparator=UTF8Type; But when I did this and triggered some logs to my syslog, which in turn triggered the cassandra insertion, the CF got somehow destroyed such that I couldn't even view the contents. But I don¹t get any errors in the worker logs at all. Has anyone had any experience with CassandraCounterBatchingBolt and if so would you mind giving me your thoughts/insight. Thanks all. Storm.0.9.0.1 Storm-cassandra 0.3.2-SNAPSHOT Cassabdra: apache-cassandra-2.0.4 sg
