You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by jb...@apache.org on 2012/03/14 05:25:54 UTC
[7/14] git commit: emphasize that YOU SHOULD USE BulkOutputFormat
emphasize that YOU SHOULD USE BulkOutputFormat
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/e7e984a2
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/e7e984a2
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/e7e984a2
Branch: refs/heads/cassandra-1.1.0
Commit: e7e984a2f420470851f5ad51ea3702d786e7ed84
Parents: e454ea6
Author: Jonathan Ellis <jb...@apache.org>
Authored: Tue Mar 13 12:21:31 2012 -0500
Committer: Jonathan Ellis <jb...@apache.org>
Committed: Tue Mar 13 12:21:31 2012 -0500
----------------------------------------------------------------------
NEWS.txt | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cassandra/blob/e7e984a2/NEWS.txt
----------------------------------------------------------------------
diff --git a/NEWS.txt b/NEWS.txt
index 592458d..a588e91 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -60,6 +60,10 @@ Features
be pinned to specfic media.
- Hadoop: a new BulkOutputFormat is included which will directly write
SSTables locally and then stream them into the cluster.
+ YOU SHOULD USE BulkOutputFormat BY DEFAULT. ColumnFamilyOutputFormat
+ is still around in case for some strange reason you want results
+ trickling out over Thrift, but BulkOutputFormat is significantly
+ more efficient.
- Hadoop: KeyRange.filter is now supported with ColumnFamilyInputFormat
- The bulk loader is not longer a fat client; it can be run from an
existing machine in a cluster.