Xuanwo opened a new issue, #5219:
URL: https://github.com/apache/opendal/issues/5219
Hi, this PR suggests that we consider introducing a layer to
handle unsupported behaviors. Not all users and use cases are concerned about
whether services support versioning; they might simply want to write code
consistently and return it as is if not supported.
---
We have similar code here:
https://github.com/apache/opendal/blob/d479ac39efa9a88e10448ad81e47292b3b4ed688/core/src/layers/complete.rs#L132-L140
I think we can create a new layer called `CapabilityCheckLayer`. By default,
opendal will not perform any capability checks. Users can enable
`CapabilityCheckLayer` to ensure the features they use are supported and behave
as expected.
`CapabilityCheckLayer` may have different modes:
- Default: just bypass all checks, like the opendal default behavior.
- Correctness: only check capability that affected correctness, for example,
write with if none match, read with version.
- All: check all capabilities.
_Originally posted by @Xuanwo in
https://github.com/apache/opendal/pull/5145#discussion_r1778959423_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
