Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

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

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

jrwest opened this issue Oct 26, 2013 · 1 comment
Milestone

Comments

@jrwest
Copy link
Contributor

jrwest commented Oct 26, 2013

otherwise you can circumvent some of the bucket type invariants.

jrwest added a commit that referenced this issue Nov 26, 2013
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
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
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
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
Copy link
Contributor Author

jrwest commented Mar 24, 2014

closing since this was fixed in #460

@jrwest jrwest closed this as completed 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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant