active and claimant bucket (type) properties should be immutable #442

Closed
jrwest opened this Issue Oct 26, 2013 · 1 comment

Comments

Projects
None yet
1 participant
@jrwest
Contributor

jrwest commented Oct 26, 2013

otherwise you can circumvent some of the bucket type invariants.

@jrwest jrwest referenced this issue in basho/riak Oct 26, 2013

Closed

Add Bucket Types to Riak #362

jrwest added a commit that referenced this issue Nov 26, 2013

added btypes_eqc to test bucket types creation invariants
the test does not yet cover crashing and chaning the claimant or waiting for
type properties to propogate to other nodes (for that we will probably need/use riak_test).
However, it does reproduce #442

jrwest added a commit that referenced this issue Nov 26, 2013

added btypes_eqc to test bucket types creation invariants
the test does not yet cover crashing and chaning the claimant or waiting for
type properties to propogate to other nodes (for that we will probably need/use riak_test).
However, it does reproduce #442

jrwest added a commit that referenced this issue Nov 26, 2013

added btypes_eqc to test bucket types creation invariants
the test does not yet cover crashing and chaning the claimant or waiting for
type properties to propogate to other nodes (for that we will probably need/use riak_test).
However, it does reproduce #442

jrwest added a commit that referenced this issue Dec 19, 2013

added btypes_eqc to test bucket types creation invariants
the test does not yet cover crashing and chaning the claimant or waiting for
type properties to propogate to other nodes (for that we will probably need/use riak_test).
However, it does reproduce #442
@jrwest

This comment has been minimized.

Show comment Hide comment
@jrwest

jrwest Mar 24, 2014

Contributor

closing since this was fixed in #460

Contributor

jrwest commented Mar 24, 2014

closing since this was fixed in #460

@jrwest jrwest closed this Mar 24, 2014

@jrwest jrwest modified the milestones: 2.0-beta, 2.0 Mar 24, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment