cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From slebre...@apache.org
Subject svn commit: r1180063 - in /cassandra/branches/cassandra-1.0.0: CHANGES.txt NEWS.txt
Date Fri, 07 Oct 2011 14:55:59 GMT
Author: slebresne
Date: Fri Oct  7 14:55:59 2011
New Revision: 1180063

URL: http://svn.apache.org/viewvc?rev=1180063&view=rev
Log:
Add missing entry to the changelog and minor update to NEWS

Modified:
    cassandra/branches/cassandra-1.0.0/CHANGES.txt
    cassandra/branches/cassandra-1.0.0/NEWS.txt

Modified: cassandra/branches/cassandra-1.0.0/CHANGES.txt
URL: http://svn.apache.org/viewvc/cassandra/branches/cassandra-1.0.0/CHANGES.txt?rev=1180063&r1=1180062&r2=1180063&view=diff
==============================================================================
--- cassandra/branches/cassandra-1.0.0/CHANGES.txt (original)
+++ cassandra/branches/cassandra-1.0.0/CHANGES.txt Fri Oct  7 14:55:59 2011
@@ -84,7 +84,7 @@ Fixes merged from 0.8 below:
  * don't bother persisting columns shadowed by a row tombstone (CASSANDRA-2589)
  * reset CF and SC deletion times after gc_grace (CASSANDRA-2317)
  * optimize away seek when compacting wide rows (CASSANDRA-2879)
- * single-pass streaming (CASSANDRA-2677, 3003)
+ * single-pass streaming (CASSANDRA-2677, 2906, 2916, 3003)
  * use reference counting for deleting sstables instead of relying on GC
    (CASSANDRA-2521, 3179)
  * store hints as serialized mutations instead of pointers to data row
@@ -97,7 +97,7 @@ Fixes merged from 0.8 below:
    (CASSANDRA-2953)
  * add paging to get_count (CASSANDRA-2894)
  * fix "short reads" in [multi]get (CASSANDRA-2643, 3157, 3192)
- * add optional compression for sstables (CASSANDRA-47, 3001, 3128)
+ * add optional compression for sstables (CASSANDRA-47, 2994, 3001, 3128)
  * add scheduler JMX metrics (CASSANDRA-2962)
  * add block level checksum for compressed data (CASSANDRA-1717)
  * make column family backed column map pluggable and introduce unsynchronized
@@ -149,6 +149,12 @@ Fixes merged from 0.8 below:
  * Reduce copies done for intra-host messages (CASSANDRA-1788, 3144)
  * support of compaction strategy option for stress.java (CASSANDRA-3204)
  * make memtable throughput and column count thresholds no-ops (CASSANDRA-2449)
+ * Return schema information along with the resultSet in CQL (CASSANDRA-2734)
+ * Add new DecimalType (CASSANDRA-2883)
+ * Fix assertion error in RowRepairResolver (CASSANDRA-3156)
+ * Reduce unnecessary high buffer sizes (CASSANDRA-3171)
+ * Pluggable compaction strategy (CASSANDRA-1610)
+ * Add new broadcast_address config option (CASSANDRA-2491)
 
 
 0.8.6

Modified: cassandra/branches/cassandra-1.0.0/NEWS.txt
URL: http://svn.apache.org/viewvc/cassandra/branches/cassandra-1.0.0/NEWS.txt?rev=1180063&r1=1180062&r2=1180063&view=diff
==============================================================================
--- cassandra/branches/cassandra-1.0.0/NEWS.txt (original)
+++ cassandra/branches/cassandra-1.0.0/NEWS.txt Fri Oct  7 14:55:59 2011
@@ -7,14 +7,15 @@ Upgrading
       by default, instead of millisecond. THIS MEANS A ROLLING UPGRADE COULD
       MIX milliseconds and microseconds, with clients talking to servers
       generating milliseconds unable to overwrite the larger microsecond
-      timestamps. If this is important for your application, you can either
-      perform a non-rolling upgrade to 1.0, or update your application first
-      to use explicit timestamps with the "USING timestamp=X" syntax.
-    - the BinaryMemtable bulk-load interface has been removed. Use the
-      sstableloader tool instead.
-    - the compaction_thread_priority setting has been removed from 
+      timestamps. If you are using CQL and this is important for your
+      application, you can either perform a non-rolling upgrade to 1.0, or
+      update your application first to use explicit timestamps with the "USING
+      timestamp=X" syntax.
+    - The BinaryMemtable bulk-load interface has been removed (use the
+      sstableloader tool instead).
+    - The compaction_thread_priority setting has been removed from
       cassandra.yaml (use compaction_throughput_mb_per_sec to throttle
-      compaction instead)
+      compaction instead).
     - CQL types bytea and date were renamed to blob and timestamp, respectively,
       to conform with SQL norms.  CQL type int is now a 4-byte int, not 8
       (which is still available as bigint).
@@ -26,21 +27,21 @@ Features
 --------
     - SSTable compression is supported through the 'compression_options'
       parameter when creating/updating a column family. For instance, you can
-      create a column family Cf using compression (using the Snappy library)
+      create a column family Cf using compression (through the Snappy library)
       in the CLI with:
         create column family Cf with compression_options={sstable_compression: SnappyCompressor}
       SSTable compression is not activated by default but can be activated or
       deactivated at any time.
     - Compressed SSTable blocks are checksummed to protect against bitrot
-    - New LevelDB-inspired compaction algorithm can be enabled by setting the 
-      Columnfamily compaction_strategy=LeveledCompactionStrategy option.  
-      Leveled compaction means you only need to keep a few MB of space free for 
+    - New LevelDB-inspired compaction algorithm can be enabled by setting the
+      Columnfamily compaction_strategy=LeveledCompactionStrategy option.
+      Leveled compaction means you only need to keep a few MB of space free for
       compaction instead of (in the worst case) 50%.
-    - Ability to use multiple threads during a single compaction.  See 
+    - Ability to use multiple threads during a single compaction. See
       multithreaded_compaction in cassandra.yaml for more details.
     - Windows Service ("cassandra.bat install" to enable)
     - A dead node may be replaced in a single step by starting a new node
-      with -Dcassandra.replace_token=<token>.  More details can be found at
+      with -Dcassandra.replace_token=<token>. More details can be found at
       http://wiki.apache.org/cassandra/Operations#Replacing_a_Dead_Node
     - It is now possible to repair only the first range returned by the
       partitioner for a node with `nodetool repair -pr`. It makes it
@@ -63,14 +64,17 @@ Other
     - The old per-ColumnFamily memtable thresholds
       (memtable_throughput_in_mb, memtable_operations_in_millions,
       memtable_flush_after_mins) are ignored, in favor of the global
-      memtable_total_space_in_mb and commitlog_total_space_in_mb settings.  
+      memtable_total_space_in_mb and commitlog_total_space_in_mb settings.
       This does not affect client compatibility -- the old options are
-      still allowed, but have no effect.  These options may be removed
+      still allowed, but have no effect. These options may be removed
       entirely in a future release.
     - Backlogged compactions will begin five minutes after startup.  The 0.8
       behavior of never starting compaction until a flush happens is usually
       not what is desired, but a short grace period is useful to allow caches
       to warm up first.
+    - The deletion of compacted data files is not performed during Garbage
+      Collection anymore. This means compacted files will now be deleted
+      without delay.
 
 
 0.8.5



Mime
View raw message