Cassandra 1.1.3 has been released, download available here
- munmap commitlog segments before rename (CASSANDRA-4337)
- (JMX) rename getRangeKeySample to sampleKeyRange to avoid returning multi-MB results as an attribute (CASSANDRA-4452)
- flush based on data size, not throughput; overwritten columns no longer artificially inflate liveRatio (CASSANDRA-4399)
- update default commitlog segment size to 32MB and total commitlog size to 32/1024 MB for 32/64 bit JVMs, respectively (CASSANDRA-4422)
- avoid using global partitioner to estimate ranges in index sstables (CASSANDRA-4403)
- restore pre-CASSANDRA-3862 approach to removing expired tombstones from row cache during compaction (CASSANDRA-4364)
- (stress) support for CQL prepared statements (CASSANDRA-3633)
- Correctly catch exception when Snappy cannot be loaded (CASSANDRA-4400)
- (cql3) Support ORDER BY when IN condition is given in WHERE clause (CASSANDRA-4327)
- (cql3) delete “component_index” column on DROP TABLE call (CASSANDRA-4420)
- change nanoTime() to currentTimeInMillis() in schema related code (CASSANDRA-4432)
- add a token generation tool (CASSANDRA-3709)
- Fix LCS bug with sstable containing only 1 row (CASSANDRA-4411)
- fix “Can’t Modify Index Name” problem on CF update (CASSANDRA-4439)
- Fix assertion error in getOverlappingSSTables during repair (CASSANDRA-4456)
- fix nodetool’s setcompactionthreshold command (CASSANDRA-4455)
- Ensure compacted files are never used, to avoid counter overcount (CASSANDRA-4436)
- Merged from 1.0:
- Push the validation of secondary index values to the SecondaryIndexManager (CASSANDRA-4240)
- (Hadoop) fix iterating through a resultset consisting entirely of tombstoned rows (CASSANDRA-4466)




















