Xuanwo
It doesn't seem related to opendal, so let's close it.
cc @jszwedko, Similar to what I mentioned in https://github.com/vectordotdev/vector/issues/7501#issuecomment-2395498188, I'm willing to start an implementation for azblob based on opendal. After these implementations, I'm eager to add documentation on how...
> FYI: me and @kwapik implemented the azblob source on our client's fork of `v0.38` and it's been working on prod for the last few months. Soon I'll start porting...
Thank you for bringing this up. I'm happy to help.
Hi, @xushiyan and @alberttwong, I'm working on this now. One blocker here is opendal doesn't support construct from url yet, I will add this support in opendal first. Tracked at...
For `CatalogLoader` trait, how about we have a `CatalogConfig` like: ```rust pub struct CatalogConfig { name: String, uri: String, warehouse: String, props: HashMap, ...others } ``` So that our CatalogLoader...
I think that's a great idea. We can add APIs like `list_namespaces_stream` and refactor `list_namespaces` to use `list_namespaces_stream` internally.
> However, if you want to move it to a independent project, I think you should sent a discuss thread to the dev mail list and go through the donation(/ip...
Hi, I believe that's related to https://github.com/apache/iceberg-rust/issues/1036
Is there a way to distribute native exetension so that users only need to add fields in composer instead? I expect users don't need to know about rust core details...