pub enum ObjectClientTrustMode {
Trusted,
VerifyOnOpen,
}Expand description
Policy for trusting or probing an object-store client during open.
This only affects object-store database opens. It does not change the database file format, WAL format, or recovery rules.
Variants§
Trusted
Trust that the supplied crate::ObjectClient satisfies Trine’s object
contract.
This is the default because normal opens should be cheap and predictable
after an adapter has already been qualified. It is not a safety proof and
it does not probe the backend during open. Use
crate::verify_object_client_contract in CI, process startup, or a
deployment health check before relying on a custom adapter in this mode.
If the adapter violates conditional-write or same-key read-after-write
semantics, Trusted open will not detect that at open time; later WAL,
lease, manifest, and recovery checks still fail closed when they can
observe corruption or fencing conflicts.
VerifyOnOpen
Run the object-client contract probe during each writable object-store open.
This mode is useful while developing a new adapter or diagnosing a provider. It writes and deletes a small temporary probe object before writer ownership is taken. That adds latency, request cost, and a permission requirement to open, and proves only the probed key at that moment. Read-only opens never run this probe.
Trait Implementations§
Source§impl Clone for ObjectClientTrustMode
impl Clone for ObjectClientTrustMode
Source§fn clone(&self) -> ObjectClientTrustMode
fn clone(&self) -> ObjectClientTrustMode
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more