ALL COVERED TOPICS

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

NAVIGATE MAIN CATEGORIES

Close

Redis Roadmap to 2.0

On April 1st, Redis is entering feature freeze phase preparing for the upcoming 2.0 version. Below is the ☞ list of remaining tasks to be completed before the release will go out:

  • Redis versioning and releases documentation
  • HSETNX, HMGET, HMSET
  • zipmaps defragmentation (merge Pieter work)
  • Input validation for integer arguments (merge Alex work)
  • BLPOP tests, in gereral ability to do multi-client tests in test-redis.tcl
  • SETEX (Set + Expire)
  • CI (continuous integration testing), with valgrind and different redis.conf
  • Virtual Memory proof reading
  • Consistency in MULTI/EXEC + AOF. Write the AOF only when EXEC finished.
  • Trace/Fix VM bug about assert (see bug2.txt)
  • Don’t save empty values in .rdb files
  • Pub/Sub: rename “class” into “channel”
  • SORT BY key->field and GET key->field
  • Create a Redis Google Group about Redis client lib. Migrate to new protocol.
  • Weeks of stress testing, source coverage tests
  • Make redis-tools better to stress test more the VM implementation
  • Pattern matching capabilites for Pub/Sub

This is definitely much more serious than Redis support for SQL.