Return-Path: 
 <user-return-29857-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
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 6BCE1D209
	for <apmail-cassandra-user-archive@www.apache.org>;
 Thu,  1 Nov 2012 21:53:49 +0000 (UTC)
Received: (qmail 97579 invoked by uid 500); 1 Nov 2012 21:53:47 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 97561 invoked by uid 500); 1 Nov 2012 21:53:47 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 97553 invoked by uid 99); 1 Nov 2012 21:53:46 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 21:53:46 +0000
X-ASF-Spam-Status: No, hits=1.7 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 (athena.apache.org: domain of ertiop93@gmail.com designates
 209.85.160.44 as permitted sender)
Received: from [209.85.160.44] (HELO mail-pb0-f44.google.com) (209.85.160.44)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 21:53:40 +0000
Received: by mail-pb0-f44.google.com with SMTP id ro8so2017999pbb.31
        for <user@cassandra.apache.org>; Thu, 01 Nov 2012 14:53:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=gR61i+XgntLlhg2JuzUsWT9yPbhHMedpxlofhqFNbDE=;
        b=AmDZ10vCSeGNlv92pdWxkr1WQ+3sj9OLJbG9V7Gnt2ObL1tGvLVogzeRudaQIFmOGf
         eHifO3M2f2GCNet8LvnFkHHjI5WxSrFpOoEKi2TgjD/hfP5xTnRPKLjL5Ze++gvDtUeu
         uWqdrCyikKJH+A7FLwWO3kT4i3RanRPlzg4o/cwc0mfuCG4Y9/bxS8XV3mq9GH7ZOmPg
         VP5neIKCF7LbOBrAR7qJybGNa60vnZjvJlbUC4V/5vgCzceqglprKXMzkNfNOcIDzcq0
         84nNgWQc14rKSwzlBKpGENwyS4Vi/gWLmcMvRUYlMmGJpvQNrP5b0J/PpbpjMiKAdtWk
         DKkA==
MIME-Version: 1.0
Received: by 10.66.85.227 with SMTP id k3mr114732957paz.79.1351806800140; Thu,
 01 Nov 2012 14:53:20 -0700 (PDT)
Received: by 10.68.14.42 with HTTP; Thu, 1 Nov 2012 14:53:20 -0700 (PDT)
In-Reply-To: 
 <CADwHx2r8e+BEaMw8uV1=7TU2OyA3JJU=vnWjEM68OZpfj2QdqA@mail.gmail.com>
References: 
 <CADwHx2r8e+BEaMw8uV1=7TU2OyA3JJU=vnWjEM68OZpfj2QdqA@mail.gmail.com>
Date: Fri, 2 Nov 2012 03:23:20 +0530
Message-ID: 
 <CADwHx2qZTi9GwSrB1H8bJJf_=qwVZ=NigDpnQrk4FeWvBqun8w@mail.gmail.com>
Subject: Re: Is it bad putting columns with composite or integer name in CF
 with ByteType comparator & validator ?
From: Ertio Lew <ertiop93@gmail.com>
To: user <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=f46d042de67520980404cd760c75
X-Virus-Checked: Checked by ClamAV on apache.org

--f46d042de67520980404cd760c75
Content-Type: text/plain; charset=ISO-8859-1

Thoughts, please ?


On Thu, Nov 1, 2012 at 7:12 PM, Ertio Lew <ertiop93@gmail.com> wrote:

> Would that do any harm or are there any downsides, if I store columns with
> composite names or Integer type names in a column family with bytesType
> comparator & validator. I have observed that bytesType comparator would
> also sort the integer named columns in similar fashion as done by
> IntegerType comparator, so why should I just lock my CF to just store
> Integer or composite named columns, would be good if I could just mix
> different datatypes in same column family, No !?

--f46d042de67520980404cd760c75
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thoughts, please ?<div class=3D"gmail_extra"><br><br><div class=3D"gmail_qu=
ote">On Thu, Nov 1, 2012 at 7:12 PM, Ertio Lew <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:ertiop93@gmail.com" target=3D"_blank">ertiop93@gmail.com</a>&gt=
;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Would that do any harm or are there any down=
sides, if I store columns with composite names or Integer type names in a c=
olumn family with bytesType comparator &amp; validator. I have observed tha=
t bytesType comparator would also sort the integer named columns in similar=
 fashion as done by IntegerType comparator, so why should I just lock my CF=
 to just store Integer or composite named columns, would be good if I could=
 just mix different datatypes in same column family, No !? =A0
</blockquote></div><br></div>

--f46d042de67520980404cd760c75--