You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by xe...@apache.org on 2012/05/25 22:50:11 UTC
git commit: update NEWS.txt to warn users about risk of
simultaneously creating CFs on different nodes before version 1.2
Updated Branches:
refs/heads/cassandra-1.1 cf9a581bf -> a7277178a
update NEWS.txt to warn users about risk of simultaneously creating CFs on different nodes before version 1.2
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/a7277178
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/a7277178
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/a7277178
Branch: refs/heads/cassandra-1.1
Commit: a7277178a15ce899a9fc248e3ed1fbaecdec3e01
Parents: cf9a581
Author: Pavel Yaskevich <xe...@apache.org>
Authored: Fri May 25 23:48:53 2012 +0300
Committer: Pavel Yaskevich <xe...@apache.org>
Committed: Fri May 25 23:49:57 2012 +0300
----------------------------------------------------------------------
NEWS.txt | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cassandra/blob/a7277178/NEWS.txt
----------------------------------------------------------------------
diff --git a/NEWS.txt b/NEWS.txt
index b87f05c..3368d98 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -68,8 +68,10 @@ Upgrading
Features
--------
- Concurrent schema updates are now supported, with any conflicts
- automatically resolved. This makes temporary columnfamilies and
- other uses of dynamic schema appropriate to use in applications.
+ automatically resolved. Please note that simultaneously running
+ ‘CREATE COLUMN FAMILY’ operation on the different nodes wouldn’t
+ be safe until version 1.2 due to the nature of ColumnFamily
+ identifier generation, for more details see CASSANDRA-3794.
- The CQL language has undergone a major revision, CQL3, the
highlights of which are covered at [1]. CQL3 is not
backwards-compatibile with CQL2, so we've introduced a