Xuanwo comments

Results 1650 comments of


                                            Xuanwo

Support `Operator::remove_all` in huaweicloud OBS Parallel File System

OpenDAL now relies on `list_with_recursive` to perform `remove_all`. If storage services support `list_with_recursive`, we treat them as flat storage services, where `/path/` is considered a flat key rather than a...

Support `Operator::remove_all` in huaweicloud OBS Parallel File System

I've removed the `bug` tag from this issue since it's more about supporting a new feature. There are no actions we can take at the S3 service level.

feat: allow using object_store as opendal's backend

Thanks a lot for building this, but I think it's better to be part of opendal's object_store integration instead of in opendal core.

feat: allow using object_store as opendal's backend

Give Github Copilot a chance.

feat: allow using object_store as opendal's backend

Thank you for this! I will start review next week (this week is bit busy)

feat: Use factory mode to init the operator instance in Python binding

I want to preserve the naming of `from_config` to make space for us to introduce [RFC-3197: Config](https://github.com/apache/incubator-opendal/pull/3197) for bindings.

feat: Use factory mode to init the operator instance in Python binding

By the way, is the API style like `from_xxx` widely used in python?

feat: Use factory mode to init the operator instance in Python binding

> Nope, a normal way I don't understand this statement. *Nope, a normal way* means it does be widely used?

feat: Use factory mode to init the operator instance in Python binding

> I mean, this is a normal style `from_xxx` in Python. Got it, thanks for sharing.

feat: Use factory mode to init the operator instance in Python binding

Seems cool, would you like to propose an RFC for python binding about this change? We can place them inside `bindings/python/docs/rfcs`. --- This is the first RFC for python binding!