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

Ready: delete_mode and tombstone documentation #1096

Merged
merged 10 commits into from Jun 23, 2014

Conversation

Projects
None yet
3 participants
@lucperkins
Copy link
Contributor

commented May 20, 2014

Addressing issues #1090, #1089, #330, and probably a few others

  • delete_mode in Riak
  • delete_mode in MDC
@lucperkins

This comment has been minimized.

Copy link
Contributor Author

commented Jun 16, 2014

Ready for review, @jhmullen. I chose to go for a more minimal approach on this one. Let me know if you think it's too stripped down.

@lucperkins lucperkins changed the title WIP: delete_mode and tombstone documentation Ready: delete_mode and tombstone documentation Jun 16, 2014

When a delete request is sent to Riak, the following process is set in
motion:

1. A tombstone object (`<<>>`) is written to N nodes (with N defined by `[[n_val|Replication Properties#n-value-and-replication]]`)

This comment has been minimized.

Copy link
@lukebakken

lukebakken Jun 18, 2014

Contributor

I think we should use vnode here instead of node, and in items 2 and 3.


There are three possible settings:

* `keep` --- Disables tombstone removal; protects against an edge case in which an object is deleted and recreated on the owning nodes while a fallback is either down or awaiting handoff

This comment has been minimized.

Copy link
@lukebakken

lukebakken Jun 18, 2014

Contributor

Again, node vs vnode.


If you are updating an object that has been deleted---or if you suspect
that an update might target a deleted object---it is recommended that
you first fetch [[vector clock]] of the object prior to updating. This

This comment has been minimized.

Copy link
@lukebakken

lukebakken Jun 18, 2014

Contributor

"you first fetch the vector clock"

FetchValue fetch = new FetchValue.Builder(loc)
.withOption(Option.DELETED_VCLOCK, true)
.build();
FetchValue.Response response =

This comment has been minimized.

Copy link
@coderoshi

coderoshi Jun 23, 2014

Contributor

:wat:


## Resources

http://lists.basho.com/pipermail/riak-users_lists.basho.com/2011-October/006048.html

This comment has been minimized.

Copy link
@coderoshi

coderoshi Jun 23, 2014

Contributor

This should be a descriptive link rather than just url

@coderoshi

This comment has been minimized.

Copy link
Contributor

commented Jun 23, 2014

+1 after minor minors

lucperkins added a commit that referenced this pull request Jun 23, 2014

Merge pull request #1096 from basho/lp/delete_mode-and-tombstones
Ready: delete_mode and tombstone documentation

@lucperkins lucperkins merged commit 9bfd938 into 2.0.0 Jun 23, 2014

@lucperkins lucperkins deleted the lp/delete_mode-and-tombstones branch Jun 23, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.