Log message:
riak updated to 1.0.2

Changes in 1.0.2

* bz1227 - badstate crash in handoff
* bz1261 - pipe mapreduce jobs fail in mixed 1.0.0/1.0.1 clusters
* bz1263 - bitcask-backed vnodes handle requests while dropping
* bz1265 - eleveldb not opened with configuration options from environment
* Two new stats categories have been added to stats - node_get_fsm_siblings
  and node_get_fsm_objsize

Changes in 1.0.1

* bz0015 - Merge js-mapreduce.org and basic-mapreduce.txt
* bz1183 - Handoff may cause riak_kv_w_reduce to over-reduce
* bz1184 - riak_kv_w_reduce should respect reduce_phase_only_1 during handoff
* bz1213 - HTTP and Javascript map phases can't use do_prereduce
* bz1225 - Exact phrase search fails on repeated words
* bz1228 - riak_core_ring_manager crashes with function clause and state
  of 'ok'
* bz1234 - Mixed 0.14/1.0.0 cluster puts can fail for clusters with more
  than N nodes
* bz1235 - vnode crashes due to receiving handoff data in deleted state
* bz1236 - riak_pipe vnode crash in Java client test suite
* bz1237 - File descriptor leak in riak_kv_bitcask_backend fold
* bz1238 - Prereduce uses map phase arg instead of reduce phase arg
* bz1242 - Handoff stops when the ring is modified by fix-up modules
* bz1243 - JSONified riak_object drops multiple index entries
* bz1244 - riak_kv_wm_object makes call to riak_client:get/3 with
  invalid type for key
* bz1249 - Backup/restore fail if ring is fixed-up
* bz1250 - bitcask partition data isn't cleaned up after handoff

Log message:
Make it easier to switch between Bitcask, Innostore and LevelDB backends.
Add LevelDB configuration directives to app.config.
Add handoff_ip to app.config.

Log message:
Update riak to 1.0.0.
Patch away symbol visibility on SunOS.

Log message:
Import riak-1.0.0rc2 as wip/riak.

Riak is a Dynamo-inspired key/value store with a distributed database
network platform that makes storing and retrieving data simple, safe
and low-cost. Riak liberates data from vulnerable centralized databases,
allowing it to escape catastrophic losses and surges while accelerating
the speed of applications. Riak has no single point of failure. Its
multiple nodes create a truly fault-tolerant system for storing any
type of mission-critical data.