Clarification on BlockingOperator and its operations

["chitralverma (via GitHub)" <gi...@apache.org>]

GitHub user chitralverma created a discussion: Clarification on BlockingOperator and its operations

I was going through the `BlockingOperator` and the functionality it provides as a sync interface right up to the lang bindings and had a few (potentially silly) questions:

1. Blocking API on rust side is a altogether new set of abstractions with does not hold the feature parity with the usual async API (concurrent/ chunked IO etc.) what was the reason to keep it so separate from its async counterpart?
2. One way to have blocking API would have been to explicitly block on operations being performed by the Async API. I think this would ensure that the feature parity is maintained between sync and async APIs. In short Blocking API could've been a `block_on` wrapper over the usual Async API.
    - Is there an issue/ cost with this approach?
    - All of the above for python bindings as well.

GitHub link: https://github.com/apache/opendal/discussions/6188

----
This is an automatically sent email for dev@opendal.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@opendal.apache.org

Re: Clarification on BlockingOperator and its operations

["yuchanns (via GitHub)" <gi...@apache.org>]

GitHub user yuchanns added a comment to the discussion: Clarification on BlockingOperator and its operations

There is a proposal to remove the duplication of introducing block operator.

FYI: https://github.com/apache/opendal/discussions/6126

GitHub link: https://github.com/apache/opendal/discussions/6188#discussioncomment-13151497

----
This is an automatically sent email for dev@opendal.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@opendal.apache.org