Add sibling-resolution functions. #257
Conversation
A resolver function takes a RiakObject and (hopefully) resolves its siblings into a single sibling. Resolvers are invoked automatically when fetching an object returns siblings. The resolver can be set on the client, the bucket, or the individual object. If the object in conflict has no resolver, the bucket's resolver will be used, and then the client's resolver if the bucket has none. The default resolver does no resolution. Also included (but not assigned) is a resolver that selects the latest sibling based on the `last_modified` property; see riak/resolver.py for more details.
ghost
assigned
| else: | ||
| raise TypeError("resolver is not a function") | ||
|
|
||
| def _set_resolver(self, value): |
There was a problem hiding this comment.
nit: I would do the typecheck on the setter
There was a problem hiding this comment.
Looks like we are first looking at the bucket, then going to the _client, so I understand why @seancribbs put it in the getter.
There was a problem hiding this comment.
I'm ok with a little paranoia.
|
Nope.
|
|
+1, belatedly
|
|
Thanks! |
Add sibling-resolution functions.
|
Last words before we bid a fond farewell to the 1.4 release? like @evanmcc i'm good with it. |
A resolver function takes a RiakObject and (hopefully) resolves its siblings into a single sibling. Resolvers are invoked automatically when fetching an object returns siblings.
The resolver can be set on the client, the bucket, or the individual object. If the object in conflict has no resolver, the bucket's resolver will be used, and then the client's resolver if the bucket has none.
The default resolver does no resolution. Also included (but not assigned) is a resolver that selects the latest sibling based on the
last_modifiedproperty; see riak/resolver.py for more details.