[
https://issues.apache.org/jira/browse/ATLAS-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18085060#comment-18085060
]
Paresh Devalia commented on ATLAS-5002:
---------------------------------------
Team
We have skip some test-case from hive-bridge addons module.
The 11 disabled HiveHookIT methods (e.g. testCTAS, testInsertIntoTable,
testColumnLevelLineage, testLineage) run real Hive SQL that triggers MapReduce
(or equivalent distributed execution): CTAS, INSERT … SELECT, export/import
with data movement, etc. They assert that the Atlas Hive hook registers
processes, lineage, and entities after execution.
They fail on the current stack (Hive 3.1.3 + JDK 17)
Atlas today uses Hive 3.1.3 (pom.xml). On JDK 9+, local MR still serializes the
query plan with Kryo. Hive 3.1.3’s serializer expects
java.util.ArrayList$SubList.parentOffset, which does not exist on modern JDKs
(HIVE-22097). Typical failure:
MapRedTask → NoSuchFieldException: parentOffset
That is a Hive + JVM compatibility bug, not an Atlas hook bug. Extra
--add-opens fixes other JDK issues (e.g. CopyOnFirstWriteProperties) but cannot
restore a removed field.
Maven Central has no newer 3.1.x release that includes this fix; the patch
exists on Hive’s 3.1 branch and in 4.x lineages, not in published 3.1.3
artifacts.
If you re-enable those tests without disabling them
You need a Hive runtime where plan serialization works on your JDK.
> Support Java 17 for build and runtime
> -------------------------------------
>
> Key: ATLAS-5002
> URL: https://issues.apache.org/jira/browse/ATLAS-5002
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Reporter: Paresh Devalia
> Assignee: Paresh Devalia
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Currently only Java 8 is supported. Java 17 is a major LTS version of Java
> and adding support would modernize our Java version support.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
