+1
Ran the following tests with the new jars in a separate project[1]:
1. Conversion from Hudi to Delta and Iceberg
2. Conversion from Iceberg to Hudi and Delta
3. Conversion from Delta to Hudi and Iceberg
4. Hudi writers with the xtable extensions properly set the field IDs in
parquet file for compatibility with Iceberg readers

- Tim

[1] https://github.com/the-other-tim-brown/xtable-testing

On Fri, Apr 18, 2025 at 2:49 AM Stamatis Zampetakis <zabe...@gmail.com>
wrote:

> Ubuntu 22.04.5 LTS, jdk-11.0.8, Apache Maven 3.6.3
>
> [OK] Checked signatures and checksums
> [OK] Release artifacts contain "apache" and "incubating" in the name
> [OK] Diff between git repo and release artifacts matches
> [OK] DISCLAIMER-WIP, LICENSE are present and correct
> [OK] Checked NOTICE file content and distribution years
> [OK] Location of the KEYS file is correct
> [OK] README contains build instructions
> [OK] No unexpected binary files (find . -type f -exec file {} \; |
> grep -v text)
> [OK] All source files have ASF headers (grep -RiL "Licensed to the
> Apache Software Foundation")
> [OK] Built from source artifacts and run tests (mvn clean install)
> [OK] Version identifier is in the expected format (0.3.0-incubating)
> [KO] Downloaded and checked the following jars from the maven staging
> repo for LICENSE, NOTICE, DISCLAIMER, and contents:
>
> xtable-api-0.3.0-incubating.jar
> xtable-aws-0.3.0-incubating-bundled.jar
> xtable-aws-0.3.0-incubating.jar
> xtable-core_2.12-0.3.0-incubating.jar
> xtable-hive-metastore-0.3.0-incubating-bundled.jar
> xtable-hive-metastore-0.3.0-incubating.jar
> xtable-hudi-support-extensions_2.12-0.3.0-incubating-bundled.jar
> xtable-hudi-support-extensions_2.12-0.3.0-incubating.jar
> xtable-hudi-support-utils-0.3.0-incubating.jar
>
> There are still some issues with the license documentation [1, 2] in
> the jars but as far as I see there are no category-x licenses involved
> so given that we are still using a DISCLAIMER-WIP I am OK with the
> release. Ideally, we should resolve them for the next release and for
> sure before becoming a TLP.
>
> +1 (binding)
>
> Best,
> Stamatis
>
> [1] https://github.com/apache/incubator-xtable/issues/700
> [2] https://github.com/apache/incubator-xtable/issues/701
>
>
>
> On Thu, Apr 17, 2025 at 8:07 AM Vinish Reddy <vin...@apache.org> wrote:
> >
> > Hi everyone,
> >
> > 0.3.0-incubating rc1 blockers have been resolved.
> >
> >    - https://github.com/apache/incubator-xtable/issues/692
> >    - https://github.com/apache/incubator-xtable/issues/693
> >
> > Please review and vote on the release candidate #2 for the version 0.3.0,
> > as follows:
> >
> > [ ] +1, Approve the release
> >
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > The complete staging area is available for your review, which includes:
> >
> > *GH release notes [1],
> >
> > * the official Apache source release and binary convenience releases to
> be
> > deployed to dist.apache.org [2], which are signed with the key with
> > fingerprint 5EFD1E91 [3],
> >
> > * all artifacts to be deployed to the Maven Central Repository, note that
> > some of these contain bundled artifacts [4]
> >
> > * source code tag "release-0.3.0-incubating-rc2" [5],
> >
> > Thanks,
> > Vinish
> >
> > [1]
> >
> https://github.com/apache/incubator-xtable/issues/678#issuecomment-2811743242
> >
> > [2]
> >
> https://dist.apache.org/repos/dist/dev/incubator/xtable/0.3.0-incubating-rc2/
> > [2] [checksum]
> >
> https://dist.apache.org/repos/dist/dev/incubator/xtable/0.3.0-incubating-rc2/apache-xtable-0.3.0-incubating.src.tgz.sha512
> > <
> https://dist.apache.org/repos/dist/dev/incubator/xtable/0.3.0-incubating-rc1/apache-xtable-0.3.0-incubating.src.tgz.sha512
> >
> >
> > [3] https://downloads.apache.org/incubator/xtable/KEYS
> >
> > [4]
> https://repository.apache.org/content/repositories/orgapachextable-1011/
> >
> > [5] [tag]
> >
> https://github.com/apache/incubator-xtable/releases/tag/0.3.0-incubating-rc2
> >
> > [5] [SHA]
> >
> https://github.com/apache/incubator-xtable/commit/9fea75ad235914e39bc8e74e41de442e4290879d
>

Reply via email to