GitHub user chitralverma added a comment to the discussion: [Feature Request]
Support creating operator from resource URI
But why make a DSN?
The problem with DSN would be that users will have to learn how to write it,
like for example with JDBC. Eventually, it all becomes inconsistent and for
users its yet another system of reference that they will have to work ahead
with.
My suggestion would be to.
- go for source-specific URLs instead which can be dropped in from one system
to another. With the URL scheme, the service backend can be inferred.
- To make this a bit flexible, we can have a system of "accepted schemes" for
each backend. In the case of HTTP storage accepted schemes can include ["http",
"https"], for Azure it can be ["adl", "abfs", "adls" ... ]. This was mentioned
in the OP as well.
- A backend must implement a parser for each of its accepted schemes.
If this is not an acceptable solution for any reason, then I would suggest to
flatten the above structure and abstract the common code via traits or
something. This would look something like,
- Storage Backend Services
- HTTP
- HTTPS
- Azure
- ADL
- ABFS
- ADLS
- FTP
- SFTP
.
.
.
.
GitHub link:
https://github.com/apache/incubator-opendal/discussions/1494#discussioncomment-5578381
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
