You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by ja...@apache.org on 2015/08/27 17:27:16 UTC
cassandra git commit: Move batch size error news to 2.2 section
(ninja)
Repository: cassandra
Updated Branches:
refs/heads/cassandra-2.2 408746c90 -> e1086bc0a
Move batch size error news to 2.2 section (ninja)
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/e1086bc0
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/e1086bc0
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/e1086bc0
Branch: refs/heads/cassandra-2.2
Commit: e1086bc0a008f7a54d0f6995c05e48f1bbbb30cf
Parents: 408746c
Author: T Jake Luciani <ja...@apache.org>
Authored: Thu Aug 27 11:26:37 2015 -0400
Committer: T Jake Luciani <ja...@apache.org>
Committed: Thu Aug 27 11:26:54 2015 -0400
----------------------------------------------------------------------
NEWS.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cassandra/blob/e1086bc0/NEWS.txt
----------------------------------------------------------------------
diff --git a/NEWS.txt b/NEWS.txt
index 2d6d927..e8db40d 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -32,6 +32,8 @@ New features
New features
------------
+ - Very large batches will now be rejected (defaults to 50kb). This
+ can be customized by modifying batch_size_fail_threshold_in_kb.
- Selecting columns,scalar functions, UDT fields, writetime or ttl together
with aggregated is now possible. The value returned for the columns,
scalar functions, UDT fields, writetime and ttl will be the ones for
@@ -167,8 +169,6 @@ Upgrading
GossipingPropertyFileSnitch instead.
- CQL2 has been removed entirely in this release (previously deprecated
in 2.0.0). Please switch to CQL3 if you haven't already done so.
- - Very large batches will now be rejected (defaults to 50kb). This
- can be customized by modifying batch_size_fail_threshold_in_kb.
- The results of CQL3 queries containing an IN restriction will be ordered
in the normal order and not anymore in the order in which the column values were
specified in the IN restriction.