This is a breaking change, isn't it? Are we breaking the language and
updating the CQL major *again*?
-- Forwarded message --
From: jbel...@apache.org
Date: Tue, Jan 10, 2012 at 2:01 PM
Subject: [1/4] git commit: note that using KEY instead of the defined
key_alias has been
, Eric Evans eev...@acunu.com wrote:
This is a breaking change, isn't it? Are we breaking the language and
updating the CQL major *again*?
-- Forwarded message --
From: jbel...@apache.org
Date: Tue, Jan 10, 2012 at 2:01 PM
Subject: [1/4] git commit: note that using KEY instead
and
updating the CQL major *again*?
-- Forwarded message --
From: jbel...@apache.org
Date: Tue, Jan 10, 2012 at 2:01 PM
Subject: [1/4] git commit: note that using KEY instead of the defined
key_alias has been removed
To: comm...@cassandra.apache.org
Updated Branches
that using KEY instead of the defined
key_alias has been removed
To: comm...@cassandra.apache.org
Updated Branches:
refs/heads/cassandra-1.0 044eb1ede - e2231a197
refs/heads/trunk a3f2e9c3b - d48a6c14f
note that using KEY instead of the defined key_alias has been removed
Project: http
On Tue, Jan 10, 2012 at 3:03 PM, Jonathan Ellis jbel...@gmail.com wrote:
Those were grandfathered in back in the day by CFMetaData.getKeyName
simply returning KEY in that case.
So if you have no key_alias defined, or it was defined to KEY, nothing
changes. But if you did define PK to be
