emkornfield commented on pull request #3691: URL: https://github.com/apache/iceberg/pull/3691#issuecomment-1017936053
> I'm wondering if the FileIO implementations need to be storage-specific. For example, pyarrow, boto, and smartopen all could be used as an implementation for various cloud storage solutions. Instead of having something like PyarrowS3FileIO to differentiate between maybe like a BotoS3FileIO, we could instead do a PyarrowFileIO which can be an entry point to any of the storage io options provided by pyarrow. I don't think this has any implications for this PR in particular so I'll work on updating this asap with the suggestions and we can tackle these other questions in follow-up discussions. Agreed, I was pointing out that for common connection types additonal dependencies can be avoided for a large number of systems if pyarrow is assumed as dependency. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
