roeap commented on issue #6350: URL: https://github.com/apache/arrow-datafusion/issues/6350#issuecomment-1547010192
> but is a non-trivial change We can leave it as is then for now and I'll observe the actual impact in production as we adopt this more and more. I did have a somewhat related question though 😆. To implement the catalog client I more or less just copied the client and auth methods out of object_store and was planning to use the same for the glue catalog integration (this still uses the deprecated rusoto crate in delta-rs) - it's quite nice to use for other mutli-cloud scenarios. I guess my question is, do you believe there may be value in having something similar to object_store for cloud catalogs or maybe expose the client and credentials? I guess object_store would not want to make a contract with its consumers on the internal http client apis, but maybe if it is made explicit that these are APIs that do not pay into the public contract and versioning guarantees? -- 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]
