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 888E2D2F0 for ; Sun, 11 Nov 2012 22:10:04 +0000 (UTC) Received: (qmail 61836 invoked by uid 500); 11 Nov 2012 22:10:02 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 61795 invoked by uid 500); 11 Nov 2012 22:10:02 -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 61786 invoked by uid 99); 11 Nov 2012 22:10:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Nov 2012 22:10:02 +0000 X-ASF-Spam-Status: No, hits=3.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,SUBJ_ALL_CAPS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rkevinburton@charter.net designates 216.33.127.82 as permitted sender) Received: from [216.33.127.82] (HELO mta31.charter.net) (216.33.127.82) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Nov 2012 22:09:53 +0000 Received: from imp11 ([10.20.200.11]) by mta31.charter.net (InterMail vM.8.01.05.02 201-2260-151-103-20110920) with ESMTP id <20121111220933.RYIF24708.mta31.charter.net@imp11> for ; Sun, 11 Nov 2012 17:09:33 -0500 Received: from KevinPC ([24.159.241.210]) by imp11 with smtp.charter.net id NN9Y1k00a4Z4VX405N9Y2T; Sun, 11 Nov 2012 17:09:33 -0500 X-Authority-Analysis: v=1.1 cv=Agrl9JAs5+GZar64di+3zu8XOh97iO5Qaqn/xe6For4= c=1 sm=1 a=yUnIBFQkZM0A:10 a=rvDZ1Ou6zk5jcJFOa7NSqA==:17 a=a5LNsaEAAAAA:8 a=mV9VRH-2AAAA:8 a=hOpmn2quAAAA:8 a=pGLkceISAAAA:8 a=PoV2f4XWwMqQkyPXLA4A:9 a=CjuIK1q_8ugA:10 a=JHKnsczD40cA:10 a=hUswqBWy9Q8A:10 a=MSl-tDqOz04A:10 a=e5V8Y3zjBzhkN7aq:21 a=NZqAtybdWE-f9atk:21 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=jk-7Eux5taXVZ_VIqiwA:9 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=NWVoK91CQyQA:10 a=gL9c4SNeA_PZLfXx:21 a=rvDZ1Ou6zk5jcJFOa7NSqA==:117 From: "Kevin Burton" To: References: <003a01cdbfc8$c134f490$439eddb0$@charter.net> <008201cdc03f$99d4b8a0$cd7e29e0$@charter.net> <7CED871F-DE30-4CDC-9325-48AD8EF9D03C@thelastpickle.com> In-Reply-To: <7CED871F-DE30-4CDC-9325-48AD8EF9D03C@thelastpickle.com> Subject: RE: CREATE COLUMNFAMILY Date: Sun, 11 Nov 2012 16:09:32 -0600 Message-ID: <00ac01cdc059$3aa8dd60$affa9820$@charter.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00AD_01CDC026.F010DE60" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJ9pWRkuwGncfkem0G12JfVIOvJUQJcE/QvAlyJBTYBpaACnZZSdNGQ Content-Language: en-us X-Virus-Checked: Checked by ClamAV on apache.org This is a multipart message in MIME format. ------=_NextPart_000_00AD_01CDC026.F010DE60 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit What happens when you are mainly concerned about the human readable formats? Say initially you don't supply metadata for a key like foo in the column family, but you get tired of seeing binary data displayed for the values so you update the column family to get a more human readable format by adding metadata for foo. Will this work? From: aaron morton [mailto:aaron@thelastpickle.com] Sent: Sunday, November 11, 2012 3:39 PM To: user@cassandra.apache.org Subject: Re: CREATE COLUMNFAMILY Also most idomatic clients use the information so they can return the appropriate type to you. Can the metadata be applied after the fact? If so how? UPDATE COLUMN FAMILY in the CLI will let you change it. Note that we do not update the existing data. This can be a problem if you do something like change a variable length integer to a fixed length one. Cheers ----------------- Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 12/11/2012, at 8:06 AM, Kevin Burton wrote: Thank you this helps with my understanding. So the goal here is to supply as many name/type pairs as can be reasonably be foreseen when the column family is created? Can the metadata be applied after the fact? If so how? -----Original Message----- From: Edward Capriolo [mailto:edlinuxguru@gmail.com] Sent: Sunday, November 11, 2012 9:37 AM To: user@cassandra.apache.org Subject: Re: CREATE COLUMNFAMILY If you supply metadata cassandra can use it for several things. 1) It validates data on insertion 2) Helps display the information in human readable formats in tools like the CLI and sstabletojson 3) If you add a built-in secondary index the type information is needed, strings sort differently then integer 4) columns in rows are sorted by the column name, strings sort differently then integers On Sat, Nov 10, 2012 at 11:55 PM, Kevin Burton wrote: I am sure this has been asked before but what is the purpose of entering key/value or more correctly key name/data type values on the CREATE COLUMNFAMILY command. ------=_NextPart_000_00AD_01CDC026.F010DE60 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

What happens when you are mainly concerned about the human readable = formats? Say initially you don’t supply metadata for a key like = foo in the column family, but you get tired of seeing binary data = displayed for the values so you update the column family to get a more = human readable format by adding metadata for foo. Will this = work?

 

From:= = aaron morton [mailto:aaron@thelastpickle.com]
Sent: Sunday, = November 11, 2012 3:39 PM
To: = user@cassandra.apache.org
Subject: Re: CREATE = COLUMNFAMILY

 

Also most = idomatic clients use the information so they can return the appropriate = type to you. 

 

 Can the metadata be applied
after the fact? = If so how?

UPDATE COLUMN = FAMILY in the CLI will let you change = it. 

Note that we do = not update the existing data. This can be a problem if you do something = like change a variable length integer to a fixed length = one. 

 

Cheers

 

-----------------

Aaron Morton

Freelance Developer

@aaronmorton

 

On = 12/11/2012, at 8:06 AM, Kevin Burton <rkevinburton@charter.net>= wrote:



Thank you = this helps with my understanding.

So the goal here is to supply = as many name/type pairs as can be reasonably
be foreseen when the = column family is created? Can the metadata be applied
after the fact? = If so how?

-----Original Message-----
From: Edward Capriolo = [mailto:edlinuxguru@gmail.com] =
Sent: Sunday, November 11, 2012 9:37 AM
To: user@cassandra.apache.orgSubject: Re: CREATE COLUMNFAMILY

If you supply metadata = cassandra can use it for several things.

1) It validates data on = insertion
2) Helps display the information in human readable formats = in tools like the
CLI and sstabletojson
3) If you add a built-in = secondary index the type information is needed,
strings sort = differently then integer
4) columns in rows are sorted by the column = name, strings sort differently
then integers

On Sat, Nov 10, = 2012 at 11:55 PM, Kevin Burton <rkevinburton@charter.net>=
wrote:

I am sure this has been asked before but = what is the purpose of
entering key/value or more correctly key = name/data type values on the
CREATE COLUMNFAMILY = command.



 

 

------=_NextPart_000_00AD_01CDC026.F010DE60--