[
https://issues.apache.org/jira/browse/IMPALA-9132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968787#comment-16968787
]
ASF subversion and git services commented on IMPALA-9132:
---------------------------------------------------------
Commit f49f8d8a32d12128eafb4c76632ca2908d22fa28 in impala's branch
refs/heads/master from Anurag Mantripragada
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=f49f8d8 ]
IMPALA-9132: Explain statements should not cause nullptr in
LogLineageRecord()
For DDLs LogLineageRecord() adds certain fields in the backend before
flushing the lineage. It uses ddl_exec_response() to get these fields.
However, explain is a special kind of DDL which does not have an
associated catalog_op_executor_. This causes explain statements to
throw NPE when ddl_exec_response() is called.
Currently, tools like atlas do not track lineages for explain
statements. This change skips lineage logging for explain statements.
In general, adds a nullptr check for catalog_op_executor_.
Testing:
Added a test to verify lineage is not created for explain statements.
Change-Id: Iccc20fd5a80841c820ebeb4edffccebea30df76e
Reviewed-on: http://gerrit.cloudera.org:8080/14646
Reviewed-by: Tim Armstrong <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Explain statements should not cause NPE in LogLineageRecord()
> -------------------------------------------------------------
>
> Key: IMPALA-9132
> URL: https://issues.apache.org/jira/browse/IMPALA-9132
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Anurag Mantripragada
> Assignee: Anurag Mantripragada
> Priority: Blocker
> Labels: crash
>
> For DDLs, LogLineageRecord() adds certain fields to the lineageGraph in the
> backend. However, explain statements do not have a catalogOpExecutor causing
> a NPE.
> We should, in general, avoid creating lineage records for Explain as Atlas
> currently does not use them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
