[
https://issues.apache.org/jira/browse/DRILL-7797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Soubusta resolved DRILL-7797.
---------------------------------
Resolution: Fixed
Don't know, what you did, but it is fixed, I verified it on TPCH data stored in
Minio in PARQUET format, decimals are no longer corrupted
> Decimals are wrongly read from parquet files
> --------------------------------------------
>
> Key: DRILL-7797
> URL: https://issues.apache.org/jira/browse/DRILL-7797
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Parquet
> Affects Versions: 1.18.0
> Reporter: Jan Soubusta
> Priority: Major
>
> My setup:
> Docker embedded Drill 1.18 (latest).
> Parquet decimals are wrongly read by Drill, wrong huge / negative values are
> displayed.
> Example small public file:
> [https://gdc-tiger-test-data-eu-central.s3.eu-central-1.amazonaws.com/other_files/tpch/supplier.parquet/a51ab8fd-v_verticadb_node0001-140644911675136-0.parquet]
> The file was exported from Vertica database using EXPORT TO PARQUET statement.
> My colleague utilizes his parquet reader written in C++ and this is his
> comment:
> {quote}
> 6th column S_ACCTBAL has type FIXED_LEN_BYTE_ARRAY and convertedType DECIMAL
> with scale 2 and precision 15.
> I would say, that it is correctly conforming specification.
> {quote}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
