I just want to add this link for those who are interested in that kv679 fix.
https://gist.github.com/russelldb/eec09409528974fb4321
There are some operational nuances that need to be considered, and the release
notes don’t link to the docs as they don’t seem to exist yet. Hopefully that
gist ca
Alex,
We require bucket types for the write-once feature for the same reason we
require them for datatypes or strong consistency: this is a property that
changing after data has been written could have undefined behavior. Making
there be an explicit creation/activation of the bucket-type ensures t
"The write_once property is applied to a bucket type"... why only on bucket
types?
ex: RIAK.bucket_type('my_type').bucket('my_bucket').get('my_key')
Normally I use bucket types to use mutable data like Maps/Sets/Counters...
so I can update its contents (multiple writes) and when I have static dat
Riak 2.1 is available [1]! Let’s start with the most fun part.
## New Feature
Riak 2.1 introduces the concept of “write once” buckets, buckets whose
entries are intended to be written exactly once, and never updated or
over-written. The write_once property is applied to a bucket type and
may only
