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 CC1F9108F9 for ; Wed, 6 Nov 2013 21:13:43 +0000 (UTC) Received: (qmail 99444 invoked by uid 500); 6 Nov 2013 21:13:41 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 99389 invoked by uid 500); 6 Nov 2013 21:13:41 -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 99381 invoked by uid 99); 6 Nov 2013 21:13:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Nov 2013 21:13:41 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ajazam@gmail.com designates 209.85.215.43 as permitted sender) Received: from [209.85.215.43] (HELO mail-la0-f43.google.com) (209.85.215.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Nov 2013 21:13:32 +0000 Received: by mail-la0-f43.google.com with SMTP id ec20so63960lab.2 for ; Wed, 06 Nov 2013 13:13:11 -0800 (PST) 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=xXv+oG4Kpi9XsmVCTrBJTwR8edQv3aQmsdD3SUG9NvI=; b=f8yTxtAUet8tYICI1Bxt5k6oXDBCku4l9VFSuOw9mvMCFlswUyivnXyYk1khLHVolG KrWfoQNHAaZT/KOrdHI/X/iddZmYtFQxyReDW3Y3nD+1fCK69bkKB6hEGFjvk4BrB9Hr +S8vk/Dj2BCcw62PMUMxek+oGKAp1iaiOMHdth2klL6h8mqDSRF8et26d9r3QSn9QyEz i4d1gBiL3Fsr2cTMsB6fx+zsb11/LkEZb6yiuf/6iYA/LoyXS/L/ESII+9kOVIJg4RvH rQeiheIHgmfu71MwYm9AQJUJHmS0B5oJMPyhAg0hlHiB5pScLtfBBLLGbBUTWS3iqDFB o5EA== MIME-Version: 1.0 X-Received: by 10.112.234.168 with SMTP id uf8mr3961267lbc.35.1383772391783; Wed, 06 Nov 2013 13:13:11 -0800 (PST) Received: by 10.112.247.35 with HTTP; Wed, 6 Nov 2013 13:13:11 -0800 (PST) In-Reply-To: References: Date: Wed, 6 Nov 2013 21:13:11 +0000 Message-ID: Subject: Re: CQL Datatype in Cassandra From: Jabbar Azam To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11c3d9b4dcc34a04ea889dab X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3d9b4dcc34a04ea889dab Content-Type: text/plain; charset=ISO-8859-1 Forget. The text value can be upto 2GB in size, but in practice it will be less. Thanks Jabbar Azam On 6 November 2013 21:12, Jabbar Azam wrote: > Hello Techy Teck, > > Couldn't find any evidence on the datastax website but found this > http://wiki.apache.org/cassandra/CassandraLimitations > > which I believe is correct. > > > Thanks > > Jabbar Azam > > > On 6 November 2013 20:19, Techy Teck wrote: > >> We are using CQL table like this - >> >> CREATE TABLE testing ( >> description text, >> last_modified_date timeuuid, >> employee_id text, >> value text, >> PRIMARY KEY (employee_name, last_modified_date) >> ) >> >> >> We have made description as text in the above table. I am thinking is >> there any limitations on text data type in CQL such as it can only have >> certain number of bytes and after that it will truncate? >> >> Any other limitations that I should be knowing? Should I use blob there? >> >> > --001a11c3d9b4dcc34a04ea889dab Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Forget. The text value can be upto 2GB in size, but in pra= ctice it will be less.

Thanks

Jabbar Azam


On 6 November 2013 21:12, Jabbar Azam <a= jazam@gmail.com> wrote:
Hello Techy Teck,

Couldn't find any= evidence on the datastax website but found this=A0http://wiki.apa= che.org/cassandra/CassandraLimitations

which I believe is correct.

<= div class=3D"gmail_extra">
Thanks

Jabbar Azam
<= /span>


On 6 November 2013 20:19, Techy Teck <comptechgeeky@gmail.com> wrote:
We are using CQL table like this -

CREAT= E TABLE testing (
=A0 description text,
=A0 last_modified_date timeuu= id,
=A0 employee_id text,
=A0 value text,
=A0 PRIMARY KEY (employe= e_name, last_modified_date)
)


We have made description as text in the above table. I a= m thinking is there any limitations on text data type in CQL such as it can= only have certain number of bytes and after that it will truncate?

Any other limitations that I should be knowing? Should I use blob= there?



--001a11c3d9b4dcc34a04ea889dab--