I think it's important for a project to remain focused on its core purpose, and I've always advocated for Iceberg to remain a library that is easy to plug into other projects. I think that should be the guide here as well. Aren't projects like Spark and Trino responsible for producing easy to use Docker images of those environments? Why would the Iceberg project build and maintain them?
I would prefer not to be distracted by these things, unless we need them for cases like supporting testing and validation of things that are part of the core purpose of the project. On Tue, Oct 8, 2024 at 6:08 AM Ajantha Bhat <ajanthab...@gmail.com> wrote: > Hello everyone, > > Now that the test fixtures are in [1],we can create a runtime JAR for the > REST catalog adapter [2] from the TCK. > Following that, we can build and maintain the Docker image based on it [3]. > > I also envision the Iceberg community maintaining some quick-start Docker > images, such as spark-iceberg-rest, Trino-iceberg-rest, among others. > > I've looked into other Apache projects, and it seems that Apache Infra can > assist us with this process. > As we have the option to publish Iceberg docker images under the Apache > Docker Hub account. > > [image: image.png] > > I am more than willing to maintain this code, please find the PRs related > to the same [2] & [3]. > > Any suggestions on the same? contributions are welcome if we agree to > maintain it. > > [1] https://github.com/apache/iceberg/pull/10908 > [2] https://github.com/apache/iceberg/pull/11279 > [3] https://github.com/apache/iceberg/pull/11283 > > - Ajantha >
