tustvold commented on issue #2230:
URL: https://github.com/apache/arrow-rs/issues/2230#issuecomment-1200126485

   I'm not sure about this, the `Path` abstraction is very specifically just 
that a `Path`. This keeps it simple and ensures consistent behaviour across 
object storage implementations. Any additional URL parameters, e.g. host, 
credentials, ports, etc... are to be handled at the ObjectStore level, i.e. 
passed to it on construction.
   
   To give an example of where ambiguity would arise, if I call the list API 
with a `URL` instead of a prefix, what should the store do, should it ignore 
the extra arguments, should the returned Path also contain these arguments?
   
   Could you perhaps expand a bit more on your use case?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to