Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 77708C811 for ; Tue, 5 Jun 2012 16:31:00 +0000 (UTC) Received: (qmail 7886 invoked by uid 500); 5 Jun 2012 16:30:57 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 7858 invoked by uid 500); 5 Jun 2012 16:30:57 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 7850 invoked by uid 99); 5 Jun 2012 16:30:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2012 16:30:57 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Edward.Sargisson@globalrelay.net designates 208.81.212.160 as permitted sender) Received: from [208.81.212.160] (HELO ex1.globalrelay.net) (208.81.212.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2012 16:30:52 +0000 Received: from [10.5.5.212] (208.81.212.224) by ex1.office.globalrelay.net (10.6.60.10) with Microsoft SMTP Server id 8.1.436.0; Tue, 5 Jun 2012 09:30:31 -0700 Message-ID: <4FCE3427.5020802@globalrelay.net> Date: Tue, 5 Jun 2012 09:30:31 -0700 From: Edward Sargisson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Subject: Performance impact of static vs dynamic columns and mixing the two in the same CF Content-Type: multipart/alternative; boundary="------------000003050207000009000407" X-Virus-Checked: Checked by ClamAV on apache.org --------------000003050207000009000407 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Hi all, A question has come up in our team about the performance impact of static vs dynamic columns. We'd like to ask two questions: Quick background: We are using a custom app to write to Cassandra using Hector. Production is Solaris and pre-prod is generally Centos. We're currently on 0.7 but will be moving to 1.1 very shortly. 1. Does specifying the type of a column affect performance other than the cost of validating data as it is stored? e.g. does it help compaction, etc? From my reading of the docs the advantage is that the data will be validated on write and that the various dev tools can deserialize into a human readable form easily. 2. Is there any impact to mixing static and dynamic columns in the same column family? (Follow-up question: is this far outside of the designers' intentions and thus unsafe?) The docs seem to indicate that the designers think of static column families and dynamic column families and *not* a mixture of the two. My mental model is that a column is just a column. It's possible to specify some metadata about columns for validation and display but that's about it. Is there something to change this model? Thanks in advance for any comments. Cheers, Edward -- Edward Sargisson senior java developer Global Relay edward.sargisson@globalrelay.net *866.484.6630* New York | Chicago | Vancouver | London (+44.0800.032.9829) | Singapore (+65.3158.1301) Global Relay Archive supports email, instant messaging, BlackBerry, Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter, Facebook and more. Ask about *Global Relay Message* *--- *The Future of Collaboration in the Financial Services World * *All email sent to or from this address will be retained by Global Relay's email archiving system. This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. Global Relay will not be liable for any compliance or technical information provided herein. All trademarks are the property of their respective owners. --------------000003050207000009000407 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Hi all,
A question has come up in our team about the performance impact of static vs dynamic columns. We'd like to ask two questions:

Quick background: We are using a custom app to write to Cassandra using Hector. Production is Solaris and pre-prod is generally Centos. We're currently on 0.7 but will be moving to 1.1 very shortly.

1. Does specifying the type of a column affect performance other than the cost of validating data as it is stored?
e.g. does it help compaction, etc?
From my reading of the docs the advantage is that the data will be validated on write and that the various dev tools can deserialize into a human readable form easily.

2. Is there any impact to mixing static and dynamic columns in the same column family? (Follow-up question: is this far outside of the designers' intentions and thus unsafe?)
The docs seem to indicate that the designers think of static column families and dynamic column families and *not* a mixture of the two.

My mental model is that a column is just a column. It's possible to specify some metadata about columns for validation and display but that's about it. Is there something to change this model?

Thanks in advance for any comments.

Cheers,
Edward


--

Edward Sargisson

senior java developer
Global Relay

edward.sargisson@globalrelay.net


866.484.6630 
New York | Chicago | Vancouver  |  London  (+44.0800.032.9829)  |  Singapore  (+65.3158.1301)

Global Relay Archive supports email, instant messaging, BlackBerry, Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter, Facebook and more. 


Ask about Global Relay Message — The Future of Collaboration in the Financial Services World


All email sent to or from this address will be retained by Global Relay’s email archiving system. This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law.  Global Relay will not be liable for any compliance or technical information provided herein.  All trademarks are the property of their respective owners.

--------------000003050207000009000407--