zeroshade commented on issue #399: URL: https://github.com/apache/iceberg-go/issues/399#issuecomment-2818932822
It's definitely not possible to remove it as a dependency entirely as we rely on it for performing the filtering and other functionality for performing scans. Though I am surprised that the compute package alone adds that much (or is that ~7mb the entire arrow-go package?) > Perhaps it would be possible to move some of the Arrow integration stuff into a sub-package, so that depending on the main "iceberg" package (which defines types like the manifests, schema, and partition spec) doesn't pull it in as an unused transitive dependency? Right now all of the Arrow stuff should be solely relegated to the `iceberg/table` package so if you're only utilizing the main `iceberg` package and not the `table` sub-package, you the compiler can exclude all of the Arrow stuff. It would be a significant chunk of work, but it might be possible to push all of the scanning and such to a sub-package which would allow most of the table operations (except scans) to not require Arrow. -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
