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: local policy)
From: "Hiller, Dean" <Dean.Hiller@nrel.gov>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Tue, 24 Sep 2013 06:36:53 -0600
Subject: =?Windows-1252?Q?is_this_correct,_thrift_unportable_to_CQL3=8A.?=
Thread-Topic: 
 =?Windows-1252?Q?is_this_correct,_thrift_unportable_to_CQL3=8A.?=
Thread-Index: Ac65Ir/KFzLE2ylmRm6V1E/C/Yp7eQ==
Message-ID: <CE66E385.3276C%Dean.Hiller@nrel.gov>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.7.130812
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Many applications in thrift use the wide row with composite column name and=
 as an example, let's say golf score for instance and we end up with golf s=
core : pk like so

null : pk56
null : pk45
89 : pk90
89: pk87
90: pk101
95: pk17

Notice that there are some who do not have a golf score(zero would not quit=
e make sense and would be interpreted as a golf score).  I am hearing from =
this post if they are correct that this is not portable to CQL3???  Is this=
 true?  http://stackoverflow.com/questions/18963248/how-can-i-have-null-col=
umn-value-for-a-composite-key-column-in-cql3

(This sounds like a major deficit to me as the wide row now can only be use=
d where actual values exist?????).  Is it possible to port this pattern to =
CQL3?

Thanks,
Dean