Fang-Yu Rao created IMPALA-14328:
------------------------------------
Summary: Produce column lineage graph when Calcite is the planner
Key: IMPALA-14328
URL: https://issues.apache.org/jira/browse/IMPALA-14328
Project: IMPALA
Issue Type: Sub-task
Components: Frontend
Reporter: Fang-Yu Rao
Assignee: Fang-Yu Rao
We found that Impala could not produce a structurally same column lineage graph
when Calcite is the planner. For instance, consider the following query in
[lineage.test|https://github.com/apache/impala/blob/master/testdata/workloads/functional-query/queries/QueryTest/lineage.test].
{code:java}
select * from (
select tinyint_col + int_col x from functional.alltypes
union all
select sum(bigint_col) y from (select bigint_col from functional.alltypes)
v1) v2
{code}
We expect Impala to produce a graph with 4 vertices and 1 edge. However, we
only get one vertice when Calcite is the planner.
{code}
{
"edges": [
{
"edgeType": "PROJECTION",
"sources": [],
"targets": [
0
]
}
],
"endTime": 1755630445,
"hash": "3968bd65781e9e856eaca799f4501513",
"queryId": "fb443702ac817ecc:c432854600000000",
"queryText": "select * from ( select tinyint_col + int_col x from
functional.alltypes union all select sum(bigint_col) y from (select
bigint_col from functional.alltypes)
"timestamp": 1755630437,
"user": "fangyurao",
"vertices": [
{
"id": 0,
"vertexId": "X",
"vertexType": "COLUMN"
}
]
}
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
