[Announcement] Riak 2.1 - Features & Release Notes
sean at basho.com
Thu Apr 16 23:19:57 EDT 2015
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 that
the behavior on the namespace created by the bucket-type never changes.
However, old or "default" buckets may be changed at any time -- meaning we
can't ensure safety of any property changes.
On Thu, Apr 16, 2015 at 3:50 PM, Alex De la rosa <alex.rosa.box at gmail.com>
> "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 data
> I use a basic buckets:
> ex: RIAK.bucket('my_bucket').get('my_key')
> It makes much more sense to me to have write_once capabilities in this
> kind of bucket that not in a bucket type bucket. I can imagine the use of a
> bucket type just for indexing data in Solr and not change it... but I think
> simple buckets would benefit of this feature even more.
> On Thu, Apr 16, 2015 at 10:40 PM, Matthew Brender <mbrender at basho.com>
>> Riak 2.1 is available ! 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 be set at bucket creation time. This allows Riak to avoid a
>> "read before write" for write_once buckets only. More information, as
>> always, is available in the docs 
>> ## Other updates
>> There are a number of GitHub Issues closed with the 2.1 release. Some
>> noteworthy updates:
>> * A nice solution for a corner case that could result in data loss 
>> * A public API related to riak_core_ring_manager thanks to Darach Ennis!
>> * A JSON writer for a number of riak_admin commands - see commit for
>> details 
>> * Updates to Yokozuna (Riak’s Solr integration) that include
>> additional metrics thanks to Jon Anderson! 
>> Be sure to see the full Release Notes here  and the Product Advisories
>> ## Upgrading
>> Be sure to review documentation  before an upgrade. It’s worth
>> noting that all nodes in a cluster must be at 2.1 before you set the
>> write_once property on a bucket.
>> It’s worth noting that there is a known issue with Yokozuna that
>> causes entry loss on AAE activity . Please keep this in mind before
>> ## Feedback please
>> Do you have a use case where write_once could be helpful? Please reply
>> to me directly! I would love to learn about your environment and be
>> able to share more details with you.
>> Developer Advocate
>>  http://docs.basho.com/riak/latest/downloads/
>>  http://docs.basho.com/riak/latest/dev/advanced/write-once
>>  https://github.com/basho/riak_kv/issues/679
>>  https://github.com/basho/riak_core/pull/716
>>  https://github.com/basho/riak_kv/pull/855
>>  https://github.com/basho/riak/blob/develop/RELEASE-NOTES.md
>>  http://docs.basho.com/riak/latest/community/product-advisories/
>>  https://github.com/basho/yokozuna/issues/481
>> riak-users mailing list
>> riak-users at lists.basho.com
> riak-users mailing list
> riak-users at lists.basho.com
Sean Cribbs <sean at basho.com>
Technical Lead, Riak
Basho Technologies, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users