[
https://issues.apache.org/jira/browse/IMPALA-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897831#comment-17897831
]
ASF subversion and git services commented on IMPALA-13541:
----------------------------------------------------------
Commit 75e012189099cba3a7f6aa66ef77dbbe0b03235c in impala's branch
refs/heads/master from Steve Carlin
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=75e012189 ]
IMPALA-13541: Calcite planner, declare explicit_cast in operator table.
This fixes a regression caused by IMPALA-13516.
The validator finds the explicit_cast function when the cast to
timestamp function is present in the query. However, the validator
then tries to validate the explicit_cast function which was not
present in the operator table. Placing the operator in the table
fixes the issue.
Change-Id: Ib8577a06178435f5048d0a9721c16069ebe05743
Reviewed-on: http://gerrit.cloudera.org:8080/22057
Reviewed-by: Michael Smith <[email protected]>
Tested-by: Michael Smith <[email protected]>
> Calcite planner: Fix explicit_cast regression in tpcds 32
> ---------------------------------------------------------
>
> Key: IMPALA-13541
> URL: https://issues.apache.org/jira/browse/IMPALA-13541
> Project: IMPALA
> Issue Type: Sub-task
> Affects Versions: Impala 4.5.0
> Reporter: Steve Carlin
> Assignee: Steve Carlin
> Priority: Major
> Fix For: Impala 4.5.0
>
>
> IMPALA-13516 caused a regression.
> The validator finds the explicit_cast function when the cast to timestamp
> function is present in the query. However, the validator then tries to
> validate the explicit_cast function which was not placed in the operator
> table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
