Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of eevans@acunu.com designates
 209.85.160.44 as permitted sender)
MIME-Version: 1.0
Date: Tue, 20 Dec 2011 16:56:13 -0600
Message-ID: 
 <CAL35Oi2PCj=3KA-fMh0zvBV4EbzzYT_MuZAq-ozwV1YkKKvD+w@mail.gmail.com>
Subject: CQL support for compound columns
From: Eric Evans <eevans@acunu.com>
To: dev@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

There has been a discussion taking place in CASSANDRA-2474[1]
regarding the language and semantics of compound columns in CQL.
Though the issue was only opened in July, and despite extended periods
of inactivity, it is monstrously long.  Additionally, the discussion
necessarily includes inline visual aids (tables, graphics, and
verbatim code snippets) that are constantly being revised, which only
compounds (pun intended) the problem.  I feel as though this is not
only making the discussion less constructive, but that it may be
scaring people off, (and IMO, this issue could use to be discussed
among a larger group anyway).

I propose two things, 1) that we move the discussion to this mailing
list, and 2) that we track the various approaches in the wiki.

For the latter of these, I've stubbed out a page[2] that would
hopefully serve as a starting point.

Thoughts?


[1]: https://issues.apache.org/jira/browse/CASSANDRA-2474
[2]: http://wiki.apache.org/cassandra/Cassandra2475

--=20
Eric Evans
Acunu |=A0http://www.acunu.com=A0| @acunu