[
https://issues.apache.org/jira/browse/IMPALA-13767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fang-Yu Rao updated IMPALA-13767:
---------------------------------
Description:
Currently for the Calcite planner in Impala, a temporary table associated with
a WITH clause is treated as a table by {{TableVisitor}} in
[CalciteMetadataHandler.java|https://github.com/apache/impala/blob/master/java/calcite-planner/src/main/java/org/apache/impala/calcite/service/CalciteMetadataHandler.java].
For instance, after the execution of "{{{}parsedNode.accept(tableVisitor){}}}"
in CalciteMetadataHandler.java, '{{{}tableVisitor.tableNames_{}}}' evaluates to
a {{HashSet}} consisting of the table names "{{{}default.t{}}}" and
"{{{}functional.alltypestiny{}}}" for the following query. It would be better
if "{{{}default.t{}}}" is not considered as a name of a table involved in the
query when we are visiting the {{SqlNode}}.
{code:java}
with t as (select * from functional.alltypestiny) select * from t;
{code}
was:
Currently a temporary table associated with a WITH clause is treated as a table
by {{TableVisitor}} in
[CalciteMetadataHandler.java|https://github.com/apache/impala/blob/master/java/calcite-planner/src/main/java/org/apache/impala/calcite/service/CalciteMetadataHandler.java].
For instance, after the execution of "{{{}parsedNode.accept(tableVisitor){}}}"
in CalciteMetadataHandler.java, '{{{}tableVisitor.tableNames_{}}}' evaluates to
a {{HashSet}} consisting of the table names "{{{}default.t{}}}" and
"{{{}functional.alltypestiny{}}}" for the following query. It would be better
if "{{{}default.t{}}}" is not considered as a name of a table involved in the
query when we are visiting the {{SqlNode}}.
{code:java}
with t as (select * from functional.alltypestiny) select * from t;
{code}
> A temporary table associated with a WITH clause should (probably) not be
> treated as a table by TableVisitor
> -----------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-13767
> URL: https://issues.apache.org/jira/browse/IMPALA-13767
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Reporter: Fang-Yu Rao
> Assignee: Fang-Yu Rao
> Priority: Major
>
> Currently for the Calcite planner in Impala, a temporary table associated
> with a WITH clause is treated as a table by {{TableVisitor}} in
> [CalciteMetadataHandler.java|https://github.com/apache/impala/blob/master/java/calcite-planner/src/main/java/org/apache/impala/calcite/service/CalciteMetadataHandler.java].
>
> For instance, after the execution of
> "{{{}parsedNode.accept(tableVisitor){}}}" in CalciteMetadataHandler.java,
> '{{{}tableVisitor.tableNames_{}}}' evaluates to a {{HashSet}} consisting of
> the table names "{{{}default.t{}}}" and "{{{}functional.alltypestiny{}}}" for
> the following query. It would be better if "{{{}default.t{}}}" is not
> considered as a name of a table involved in the query when we are visiting
> the {{SqlNode}}.
> {code:java}
> with t as (select * from functional.alltypestiny) select * from t;
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
