Is your feature request related to a problem or challenge? Please describe what you are trying to do.
For many storage services there exists standardized, or de-facto standardized uri formats (e.g. s3://<bucket>/path/to/blob for AWS S3 services) and are often the entry point in applications for referencing storage locations. While it is often straight forward to work with these, I made the experience that there are always edge cases to consider and keep on implementing similar logic in different projects.
Had a small discussion around this with @wjones127 in delta-io/delta-rs#721
cc @tustvold @alamb
Describe the solution you'd like
Provide a dedicated implementation for parsing storage uris within the object_store crate and maybe offer a somewhat higher level API that selects stores based on the results. As a plus this would encourage unified handling among all adopters of the crate.
Describe alternatives you've considered
Letting consumers of object_store take care of this.
Additional context
If we decide to follow this, I'd be happy to come up with a proposal. Hoping that this would just be a fairly thin wrapper around Url.
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
For many storage services there exists standardized, or de-facto standardized uri formats (e.g.
s3://<bucket>/path/to/blobfor AWS S3 services) and are often the entry point in applications for referencing storage locations. While it is often straight forward to work with these, I made the experience that there are always edge cases to consider and keep on implementing similar logic in different projects.Had a small discussion around this with @wjones127 in delta-io/delta-rs#721
cc @tustvold @alamb
Describe the solution you'd like
Provide a dedicated implementation for parsing storage uris within the object_store crate and maybe offer a somewhat higher level API that selects stores based on the results. As a plus this would encourage unified handling among all adopters of the crate.
Describe alternatives you've considered
Letting consumers of object_store take care of this.
Additional context
If we decide to follow this, I'd be happy to come up with a proposal. Hoping that this would just be a fairly thin wrapper around
Url.