[ 
https://issues.apache.org/jira/browse/IMPALA-12925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wenzhe Zhou resolved IMPALA-12925.
----------------------------------
    Fix Version/s: Impala 4.4.0
       Resolution: Fixed

> Fix decimal data type for external JDBC table
> ---------------------------------------------
>
>                 Key: IMPALA-12925
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12925
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Frontend
>            Reporter: Wenzhe Zhou
>            Assignee: Wenzhe Zhou
>            Priority: Major
>             Fix For: Impala 4.4.0
>
>
> The data types in unit-test table alltypes do not include decimal. The data 
> type of column partsupp.ps_supplycost is decimal(12,2).
> Create an external JDBC table to query table tpch.partsupp on remote Impala 
> cluster.  Select statement on the JDBC table return wrong values for column 
> partsupp.ps_supplycost. Lots of returned values are negative. 
> Decimal type is listed as supported primitive data type in 
> DataSourceTable.java(https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/catalog/DataSourceTable.java#L153).
> But it seems the data type is not handled properly which cause wrong value 
> returned from backend DataSourceScanNode.
> Another issue is that the decimal data type is not handled in frontend 
> DataSourceScanNode.java 
> (https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/planner/DataSourceScanNode.java#L152)
>  so that decimal type of predicates cannot be  pushed down.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to