Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of edlinuxguru@gmail.com
 designates 74.125.82.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAK4eHaqv1o1wsZfM2x3DPUkUsTrFuJ-QFMZRowYsJr+X_Wq1iQ@mail.gmail.com>
References: 
 <CAK4eHaqv1o1wsZfM2x3DPUkUsTrFuJ-QFMZRowYsJr+X_Wq1iQ@mail.gmail.com>
Date: Thu, 7 Feb 2013 22:09:32 -0500
Message-ID: 
 <CAENxBwxB2jczdaPoEFPtnQ85uSZ=hbMP=VAJAPhVomHdL8uqnw@mail.gmail.com>
Subject: Re: Why CQL returns data in byte format, while Hive de-serialize and
 return the data in readable format
From: Edward Capriolo <edlinuxguru@gmail.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=089e0149331a643a1204d52de377

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

In cql3 a column must be all the same type . Since cql transposes columns
the only thing they can be is byte array. Cql2 is better at compact tables
in. This regard.


On Thursday, February 7, 2013, Dinusha Dilrukshi wrote:

> Hi,
>
> We are using same underlying column family and extract the data using Hive
> query and CQL query.
> Column family meta data contains Comparator='IntegerType'
>  and default_validation_class = FloatType.
>
> CREATE COLUMN FAMILY cpu_avg_5min
> WITH COMPARATOR = 'IntegerType'
>  AND key_validation_class = UTF8Type
>  AND default_validation_class = FloatType;
>
> Queering through Hive using a Hive query returns readable data while
> queering using CQL returns byte format.
>
> Hive query result:
> localhost:8282 1350465600 71.0
> localhost:8282 1350466500 69.0
>
> CQL query result:
>  localhost:8282 | 232340574229062120517680 | 1.0561e-05
>  localhost:8282 | 232340574229062137229360 | 2.7594e-06
>
> Can someone explains the above behavior ?
>
> Regards,
> DInusha.
>

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

In cql3 a column must be all the same type . Since cql transposes columns t=
he only thing they can be is byte array. Cql2 is better at compact tables i=
n. This regard.<div><span></span><br><br>On Thursday, February 7, 2013, Din=
usha Dilrukshi  wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi,<div><br></div><div>We are using same=A0u=
nderlying column family and extract the data using Hive query and CQL query=
.=A0</div>
<div>Column family meta data contains Comparator=3D&#39;IntegerType&#39; =
=A0and=A0default_validation_class =3D FloatType.</div>
<div><br></div><div>CREATE COLUMN FAMILY cpu_avg_5min=20
<br>
WITH COMPARATOR =3D &#39;IntegerType&#39;=20
<br>
=A0AND key_validation_class =3D UTF8Type
<br>
=A0AND default_validation_class =3D FloatType; =A0</div><div><br></div><div=
>Queering through Hive using a Hive query returns readable data while queer=
ing using CQL returns byte format.</div><div><br></div><div>Hive query resu=
lt:</div>

<div>localhost:8282 	1350465600 	71.0
<br>
localhost:8282 	1350466500 	69.0=A0</div><div><br></div><div>CQL query resu=
lt:</div><div>=A0localhost:8282 | 232340574229062120517680 | 1.0561e-05
<br>
=A0localhost:8282 | 232340574229062137229360 | 2.7594e-06=A0
</div><div><br></div><div>Can someone explains the above=A0behavior ?</div>=
<div><br></div><div>Regards,</div><div>DInusha.</div>
</blockquote></div>

--089e0149331a643a1204d52de377--