You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/06/03 17:32:00 UTC
[jira] [Commented] (ATLAS-4322) Hive HOOK fails with NPE while
processing column-rename
[ https://issues.apache.org/jira/browse/ATLAS-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17356609#comment-17356609 ]
ASF subversion and git services commented on ATLAS-4322:
--------------------------------------------------------
Commit ff0c65a49fb4617b85a5b8a674be53305f5cf64b in atlas's branch refs/heads/master from JP Li
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ff0c65a ]
ATLAS-4322: Hive HOOK NPE
Signed-off-by: sidmishra <si...@apache.org>
> Hive HOOK fails with NPE while processing column-rename
> -------------------------------------------------------
>
> Key: ATLAS-4322
> URL: https://issues.apache.org/jira/browse/ATLAS-4322
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Reporter: Radhika Kundam
> Assignee: Radhika Kundam
> Priority: Trivial
>
> While processing column-rename on temporary table, Atlas hook for Hive fails with Null Pointer Exception.
> {code:java}
> 2021-05-25 15:06:38,131 ERROR org.apache.atlas.hive.hook.HiveHook: [HiveServer2-Background-Pool: Thread-529]: HiveHook.run(): failed to process operation ALTERTABLE_RENAMECOL java.lang.NullPointerException: null at java.util.ArrayList.<init>(ArrayList.java:178) ~[?:1.8.0_292] at org.apache.atlas.hive.hook.events.AlterTableRenameCol.getHiveMessages(AlterTableRenameCol.java:76) ~[hive-bridge-2.1.0.7.2.9.1-2.jar:2.1.0.7.2.9.1-2] at org.apache.atlas.hive.hook.events.AlterTableRenameCol.getNotificationMessages(AlterTableRenameCol.java:55) ~[hive-bridge-2.1.0.7.2.9.1-2.jar:2.1.0.7.2.9.1-2] at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:252) [hive-bridge-2.1.0.7.2.9.1-2.jar:2.1.0.7.2.9.1-2] at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:52) [hive-bridge-shim-2.1.0.7.2.9.1-2.jar:2.1.0.7.2.9.1-2]{code}
>
> In ATLAS-2757 a similar issue was fixed (in 2018) by adding a check for {{baseMsgs}}
> but in ATLAS-3148 it was re-introduced (in 2019).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)