Xuanwo

I'm interested in implementing this. --- I don't want it to be interactive. I'm not comfortable with requiring every release manager to operate things through a TUI. My current idea...

# My plans for this week ## backon - [x] https://github.com/Xuanwo/backon/issues/90 ## OpenDAL - [ ] OpenDAL v0.49.2 release. - [x] https://github.com/apache/opendal/pull/5064 ## Thrift - [ ] https://github.com/apache/thrift/pull/3027

# Projects I plan to help actively help review / push forward ## Paimon - [ ] https://github.com/apache/paimon-rust/pull/59 - [ ] https://github.com/apache/paimon-rust/issues/34 - [ ] https://github.com/apache/paimon-rust/pull/63

> Can it be understood in this way? Not exactly. I expect all services to be initiated from the URI. The discussion is mainly talking about whether to init services...

> Hi @Xuanwo, is this up for grabs? Thank you! I think we need to finish https://github.com/apache/incubator-opendal/issues/3240 first.

> Is there any word on whether this will be available in an upcoming release? Hi, there's no effort for this task. Perhaps you could contact @BohuTANG for your needs?

Thanks a lot for the quick feedback. > About the idea, IIUC, foyer is supposed to be a cache layer for opendal, instead of using opendal as a device (storage...

Nice catch! OpenDAL has some limitations on path to make sure all services behave like the same: https://github.com/apache/opendal/blob/918f9c07b2675eb69e8b56d4cf6e0c0631666165/core/src/raw/path.rs#L85-L96 Maybe we should raise an error for invalid path instead.

related to https://github.com/datafuselabs/databend/issues/7482

Hi, which version are you using? The latest version will set correct chunk for every storage service.