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 1113D9BA7 for ; Thu, 8 Dec 2011 05:14:01 +0000 (UTC) Received: (qmail 17894 invoked by uid 500); 8 Dec 2011 05:13:59 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 17848 invoked by uid 500); 8 Dec 2011 05:13:58 -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 17815 invoked by uid 99); 8 Dec 2011 05:13:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Dec 2011 05:13:57 +0000 X-ASF-Spam-Status: No, hits=1.6 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rajkumar.w93@gmail.com designates 74.125.82.44 as permitted sender) Received: from [74.125.82.44] (HELO mail-ww0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Dec 2011 05:13:49 +0000 Received: by wgbdr13 with SMTP id dr13so2183269wgb.25 for ; Wed, 07 Dec 2011 21:13:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=4vzQon6rQlkHbIeiEkb76TWVPUjrC9rY8bSBgYKYlSI=; b=VMDixoyHAOY2gOosgMbkl6O1HcpT6PfEoT0zVPXEl0O8OoDf36vlD/NHbz6TFT6f1R B48Y7W+5/n1H+La7Qlq21DTK9N4urIHff7SGQxWKlVc6trjBD0zT1xk7fpqWcvAFT8X5 uv8Gy23+UNXblsQJxO66j+/NmmouEHh5VMMy8= MIME-Version: 1.0 Received: by 10.227.207.206 with SMTP id fz14mr1439173wbb.7.1323321209370; Wed, 07 Dec 2011 21:13:29 -0800 (PST) Sender: rajkumar.w93@gmail.com Received: by 10.223.83.199 with HTTP; Wed, 7 Dec 2011 21:13:29 -0800 (PST) Date: Thu, 8 Dec 2011 10:43:29 +0530 X-Google-Sender-Auth: huHnbe-mux7QY8RM-KvyJ4Z5RL0 Message-ID: Subject: Composite columns vs Protocol Buffers when all you need is to pack many things in a single column From: Asil Klin To: user Content-Type: multipart/alternative; boundary=0015175d094c9bb73604b38dbacb X-Virus-Checked: Checked by ClamAV on apache.org --0015175d094c9bb73604b38dbacb Content-Type: text/plain; charset=ISO-8859-1 I know Composite columns are used for some very useful scenarios(like to replace super columns) which cannot be helped with anything else. But, for situations when you just need to pack many things in a single column efficiently and such that the retrievals are also performant, which one should be used ? (I need to store the serialized data as column value.) --0015175d094c9bb73604b38dbacb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I know=A0Composite columns are used for some very =A0useful scenarios(like = to replace=A0super columns) which cannot be helped with anything else.=A0But, for situations when you just need to pack many things in a single c= olumn efficiently and such that the retrievals are also performant, which o= ne should be used ?

(I need to store the serialized data as column value.)<= /div> --0015175d094c9bb73604b38dbacb--