zeroshade commented on issue #696: URL: https://github.com/apache/iceberg-go/issues/696#issuecomment-3792726277
This is actually something similar that I was discussing with a few others that were having an issue with the gocloud.dev dependency. Currently for the catalogs we have a registration config that allows for the go compiler to leave out catalog implementations that aren't being used. I've been considering doing something similar for the io management too. We've already isolated everything to the interfaces so it shouldn't be difficult to do a similar registration pattern for handling the io location handling. Would you be willing to contribute something to this extent (or something like what you're suggesting)? -- 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]
