org> wrote:
> >> >>> >>
> >> >>> >> +1 — excited to see this happen!
> >> >>> >>
> >> >>> >> For the TCK, I think we can release this with the Java together,
> and have a nightly build (tag th
er with nightly Dockerhub). This
>> >>> >> way we can already test out (and start implementing) the new features
>> >>> >> in the related projects. Thoughts on that?
>> >>> >>
>> >>> >>> Regarding
>> >>
> >>> >> Let's split out that discussion. My take on that is that we want to
> defer that to the query engines. In an ideal situation, the Iceberg
> integration should be part of the project itself (e.g. with Hive 4 where it
> is maintained by Hive itse
ly support.
>>> >>
>>> >>
>>> >> Let's split out that discussion. My take on that is that we want to
>>> >> defer that to the query engines. In an ideal situation, the Iceberg
>>> >> integration should be part of the pro
ines. In an ideal situation, the Iceberg
>>> integration should be part of the project itself (e.g. with Hive 4 where it
>>> is maintained by Hive itself). For Spark itself, it only requires a runtime
>>> to be added through the packages argument, and would love to s
> is maintained by Hive itself). For Spark itself, it only requires a runtime
>> to be added through the packages argument, and would love to see if we can
>> avoid maintaining images for that.
>> >>
>> >> Kind regards,
>> >> Fokko
>> &g
a runtime
> to be added through the packages argument, and would love to see if we can
> avoid maintaining images for that.
> >>
> >> Kind regards,
> >> Fokko
> >>
> >>
> >> Op do 14 nov 2024 om 18:16 schreef Christian Thiel <
> chri
Christian Thiel
>> :
>>>
>>> +1 for this as well – for us especially the REST TCK image would be nice.
>>>
>>>
>>>
>>> From: Bryan Keller
>>> Date: Thursday, 14. November 2024 at 17:13
>>> To: dev@iceberg.apache.org
&
g images for that.
>
> Kind regards,
> Fokko
>
>
> Op do 14 nov 2024 om 18:16 schreef Christian Thiel
> :
>
>> +1 for this as well – for us especially the REST TCK image would be nice.
>>
>>
>>
>> *From: *Bryan Keller
>> *Date: *Thursday, 14
sday, 14. November 2024 at 17:13
> *To: *dev@iceberg.apache.org
> *Subject: *Re: [PROPOSAL] Create Iceberg DockerHub repository
>
> +1 this would be great! Thanks JB.
>
>
>
> -Bryan
>
>
>
> On Nov 14, 2024, at 8:30 AM, Ajantha Bhat wrote:
>
>
>
> +1 f
+1 for this as well – for us especially the REST TCK image would be nice.
From: Bryan Keller
Date: Thursday, 14. November 2024 at 17:13
To: dev@iceberg.apache.org
Subject: Re: [PROPOSAL] Create Iceberg DockerHub repository
+1 this would be great! Thanks JB.
-Bryan
On Nov 14, 2024, at 8:30 AM
+1 this would be great! Thanks JB.
-Bryan
> On Nov 14, 2024, at 8:30 AM, Ajantha Bhat wrote:
>
> +1 for setting up the DockerHub repo,
>
> We discussed about this already in
> https://www.mail-archive.com/dev@iceberg.apache.org/msg07888.html
>
> Now that the Docker image PR is ready for the
+1 for setting up the DockerHub repo,
We discussed about this already in
https://www.mail-archive.com/dev@iceberg.apache.org/msg07888.html
Now that the Docker image PR is ready for the REST catalog adapter, we can
proceed with setting up the DockerHub repository.
Regarding the Kafka Connect Dock
Hi JB,
That sounds great!!
The REST TCK /adapter docker image will be super useful for the Iceberg
subprojects as it will ensure that they have access to a light-weight REST
Catalog Server image with the latest features to run integration tests against.
Sung
On 2024/11/14 15:41:04 Jean-Baptis
Hi folks,
While reviewing https://github.com/apache/iceberg/pull/11283, we
discussed having a DockerHub repository for Iceberg.
I can create this repository, similar to other Apache projects (like
for example https://hub.docker.com/r/apache/activemq-classic,
https://hub.docker.com/r/apache/airflo
15 matches
Mail list logo