Tracking issues of RFC-5444: Operator From Uri

[Xuanwo]

• RFC: RFC-5444: Operator From Uri #5444

[jorgehermo9]

Hi

I would like to start working on this.

I think it would be too much to implement all the Configurator::from_uri methods for all services at once in a single PR. Should I split it into:

First, initial implementation PR addressing

opendal/core/src/docs/rfcs/5444_operator_from_uri.md

Line 54 in 86d6c42

1. The `OperatorFactory` and `OperatorRegistry`:

OperatorRegistry and etc, but using a default implementation of Configurator::from_uri such as

pub trait Configurator{
 pub fn from_uri(uri: &str, options: impl IntoIterator<Item = (String, String)>) -> Result<Self> {
  todo!()
 }
}

and finally, implement Configurator::from_uri for each service (and remove that default implementation) in follow-up Prs?

[Xuanwo]

OperatorRegistry and etc, but using a default implementation of Configurator::from_uri such as

Hi, I believe most services can simply use the default implementations. Only specific ones, like s3 and azblob, need to implement their own. So it's will be a great start to just implement the default implementations first.

[jorgehermo9]

Hi @Xuanwo

I see that ofs uses something similar to this but in a rudimentary way, as the core lack this functionality before this implementation.

Should we create a new issue to use Operator::from_uri (once this issue is addressed) in

opendal/bin/ofs/src/main.rs

Line 66 in 52c96bb

let backend = Operator::via_iter(scheme, op_args)?;

so ofs supports ALL the available operators instead of just s3 and fs?

opendal/bin/ofs/README.md

Line 15 in 52c96bb

`ofs` is a work in progress. we only support `fs` and `s3` as backend on `Linux` currently.