Return-Path: X-Original-To: apmail-storm-user-archive@minotaur.apache.org Delivered-To: apmail-storm-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B888B105CA for ; Tue, 11 Feb 2014 03:24:04 +0000 (UTC) Received: (qmail 9541 invoked by uid 500); 11 Feb 2014 03:24:03 -0000 Delivered-To: apmail-storm-user-archive@storm.apache.org Received: (qmail 9153 invoked by uid 500); 11 Feb 2014 03:24:00 -0000 Mailing-List: contact user-help@storm.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@storm.incubator.apache.org Delivered-To: mailing list user@storm.incubator.apache.org Received: (qmail 9145 invoked by uid 99); 11 Feb 2014 03:23:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Feb 2014 03:23:58 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,MIME_QP_LONG_LINE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of boneill42@gmail.com designates 209.85.216.41 as permitted sender) Received: from [209.85.216.41] (HELO mail-qa0-f41.google.com) (209.85.216.41) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Feb 2014 03:23:53 +0000 Received: by mail-qa0-f41.google.com with SMTP id w8so10993652qac.28 for ; Mon, 10 Feb 2014 19:23:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:user-agent:date:subject:from:to:message-id:thread-topic :references:in-reply-to:mime-version:content-type; bh=h7QbNRNXSvE7BPGgZVmBVhHb0rrGEb7YsK3e+UrKyLE=; b=ka5bKne6KcqO8KZu4USa2aAALL70gJBDpGFchcGp8BXuFwrzM7CTsK1UGqt9M+QkwG VmCwXItYEywFTzcGgn+YZ2XkZH0NIAqv62k1/kwAtiZXWsDQPaipiV54LLYcOlRehmqp VnY3/LGSeRYMh0HerXfq57kpCMP55Chc5ChFOK3XUWe86+N10rZ5Q4Tub/lWF45wXGy0 q3fox2LZreT4djpEsElfjsVoM8UkZAKu/1KTfS5xUkuyKxhiT+stuznJvJez9P4pTrNh vwjHg6vpXq/0gHzOkG52C2tciyps9gtq+LMbpJzJyM9Z79vSF2O464OLPPhueID0CAUf hXLA== X-Received: by 10.224.36.129 with SMTP id t1mr50191997qad.8.1392089013147; Mon, 10 Feb 2014 19:23:33 -0800 (PST) Received: from [10.0.0.5] (c-69-242-61-131.hsd1.nj.comcast.net. [69.242.61.131]) by mx.google.com with ESMTPSA id i38sm26933166qge.1.2014.02.10.19.23.30 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 10 Feb 2014 19:23:32 -0800 (PST) Sender: "Brian O'Neill" User-Agent: Microsoft-MacOutlook/14.3.9.131030 Date: Mon, 10 Feb 2014 22:23:26 -0500 Subject: Re: Storm Cassandra and the CassandraCounterBatchingBolt From: Brian O'Neill To: Message-ID: Thread-Topic: Storm Cassandra and the CassandraCounterBatchingBolt References: In-Reply-To: Mime-version: 1.0 Content-type: multipart/alternative; boundary="B_3474915811_14673961" X-Virus-Checked: Checked by ClamAV on apache.org > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3474915811_14673961 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable 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 woul= d 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-cassandr= a 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 =80 King of Prussia, PA =80 19406 M: 215.588.6024 =80 @boneill42 =80 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. =20 From: "Gorman, Steve A." Reply-To: Date: Monday, February 10, 2014 at 4:01 PM To: "user@storm.incubator.apache.org" Subject: Storm Cassandra and the CassandraCounterBatchingBolt All,=20 I am getting an error using the CassandraCounterBatchingBolt complaining of an =8A.=20 invalid operation for non commutative column family LogVolumeByMinute I am following a tutorial from a book which is using Casandra to store tex= t in a Column Family and auto-increment a counter column. I read that in orde= r 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=3DCounterColumnType and key_validation_class=3DUTF8Typ= e and comparator=3DUTF8Type; 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=B9t get any errors in the worker logs at all. Has anyone had any experience with CassandraCounterBatchingBol= t 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 --B_3474915811_14673961 Content-type: text/html; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable

Steve,

You may want to cross post this over on the Cassandra= list.  Obviously, there should be nothing that you can do from a clien= t-perspective that would render the contents of a CF unreadable.  

What was the output in cqlsh when you tried to select f= rom the table?

The storm-cassandra implementat= ion 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 b= eing made in order to get steps to reproduce.

-brian

---

Brian O'Neill

Chief Technology Officer


Health Market&nbs= p;Science

The Science of Better Results

2700 Horizon Drive <= span style=3D"color: rgb(237, 26, 52); position: relative; top: -0.5pt; letter= -spacing: -0.4pt; ">•&nb= sp;King of Prussia, PA • 19406

M: 215.588.6024 • @boneill42  = 226;  <= /p>

healthmarketscience.com


This information transmitted in this = email message is for the intended recipient only and may contain confidentia= l and/or privileged material. If you received this email in error and are no= t the intended recipient, or the person responsible to deliver it to the int= ended recipient, please contact the sender at the email above and delete thi= s email and any attachments and destroy any copies thereof. Any review, retr= ansmission, dissemination, copying or other use of, or taking any action in = reliance upon, this information by persons or entities other than the intend= ed recipient is strictly prohibited.

 


From: "Gorman, Steve A." <STEPHEN.A.GORMAN@leidos.com>
Reply-To: <use= r@storm.incubator.apache.org>
Date:= Monday, February 10, 2014 at 4:01 PM
To: "user@storm= .incubator.apache.org" <user@storm.incubator.apache.org>
Subject: Storm Cassandra and the CassandraCounterBatchingBolt
<= /div>

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 usi= ng Casandra to store text in a Column Family and auto-increment a counter co= lumn. I read that in order to use a counter column I had to have a default_<= span style=3D"font-style: italic;">validation_class of type CounterColumnType. So I created a CF like so

<= div>create column family = LogVolumeByMinute with default_validation_class=3DCounterColumnType and key_va= lidation_class=3DUTF8Type and comparator=3DUTF8Type;



  But when I did this and triggered some logs to m= y 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 a= ny experience with CassandraCounterBatchingBolt and if so would you mind giv= ing me your thoughts/insight.

Thanks all.

Storm.0.9.0.1
Storm-cassandra 0.3.2-SNAPSHOT
=
Cassabdra: apac= he-cassandra-2.0.4
sg



--B_3474915811_14673961--