salimTutuncu commented on issue #921:
URL: 
https://github.com/apache/incubator-xtable/issues/921#issuecomment-5541368644

   Related gap on the same docs page, found while validating the published 
0.4.0 artifact: the "reuses the Hudi, Iceberg and Delta libraries your cluster 
already has" statement needs version qualifiers, because the bundle is only 
binary-compatible with specific engine versions. Exact measured results (local, 
upstream OSS binaries):
   
   | Engine dependency | Works | Fails (NoSuchMethodError) |
   |---|---|---|
   | Hudi source reader | 0.14.1 | 0.15.0, 1.0.2 
(`HoodieTableMetaClient$Builder.setConf(Configuration)`) |
   | Delta Kernel | 4.0.0 | 3.3.0 (`Snapshot.getVersion()`) |
   | Iceberg target | 1.9.2 | not tested beyond 1.9.2 |
   
   We have not tested vendor-patched builds or any versions beyond that table, 
so it is deliberately narrow. For managed-runtime relevance (per vendor 
documentation, not our tests): AWS Glue 5.1 lists Hudi 1.0.2 and Delta 3.3.2 
(https://docs.aws.amazon.com/glue/latest/dg/release-notes.html), while Amazon 
EMR 7.1 lists Hudi 0.14.1 
(https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-710-release.html), so 
depending on the platform release, users either hit the mismatch as a runtime 
`NoSuchMethodError` or are unaffected.
   
   Suggestion: alongside the Kernel auto-select fix, add a short 
engine-compatibility note for the 0.4.0 artifact to this page (tested-works: 
Hudi 0.14.1, Delta Kernel 4.0.0, Iceberg 1.9.2; tested-incompatible: Hudi 
0.15.0 and 1.0.2, Kernel 3.3.0), so the "reuses your cluster's libraries" 
sentence carries its real preconditions. Note this compatibility warning 
concerns the 0.4.0 artifact; current `main` compiles against Hudi 1.2.0 (pom, 
checked 2026-09-04).
   


-- 
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]

Reply via email to