ajtack/riak-cpp — Issue #15: Read/Write abortion on "Unresolvable Siblings" error
Author: ajtack
Created: 2012-01-29 12:19:01+00:00
State: open

> "If debugging is the process of removing bugs, then programming must be the process of putting them in."

Currently, failure to resolve siblings (by throwing an exception, for instance) will cause undefined behavior and leaking. Users need to be able to abort a read or write if they encounter a sibling set that they cannot resolve. Their server can then report an error that allows them to resolve the case.

Suggest:
1. A new error code `riak::errc::unresolvable_siblings` to report as the reason for the failed read/write to the application.
2. An exception type (maybe `riak::unresolvable_siblings`? Check how to interact with `system_error`.) that sibling resolution routines can throw when they get into trouble.