NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter



Redis 2.2: An Optimization Release

Salvatore Sanfilippo summarizes the new Redis release in the Hacker News thread:

2.2 was exactly an “optimization” release, to bring what we had at a better level of maturity.

Basically we’ll try hard to don’t add things to the API in the next releases, but just to open to new use cases changing the “backend” part, with cluster support for large fault tolerant deployment, and with diskstore for “bigdata”.

However there are a few important new things in Redis 2.2 from the point of view of the features, I think the main ones are:

  • non blocking replication, so that now slaves are able to serve data even when trying to resync with the master.
  • Check and Set with WATCH.
  • Write operations against keys with an expire set.
  • LRU eviction of keys in ‘maxmemory’ mode.
  • Support for SETBIT/GETBIT/SETRANGE/GETRANGE, basically this turn the string data type into a random access array.

The more verbose release notes are available here.

Redis 2.2 is a drop in replacement for the previous 2.0 version. Though there are some changes in the return values for edge cases.

Update: Minutes ago, Salvatore has announced that there will be a new release today to fix an urgent bug in SPOP.

Update: Redis 2.2.1 is out. You can get it from here.

Original title and link: Redis 2.2: An Optimization Release (NoSQL databases © myNoSQL)