You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/08/04 09:36:00 UTC
[jira] [Updated] (HIVE-25420) Ignore time type column in Iceberg
testing for vectorized runs
[ https://issues.apache.org/jira/browse/HIVE-25420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HIVE-25420:
----------------------------------
Labels: pull-request-available (was: )
> Ignore time type column in Iceberg testing for vectorized runs
> --------------------------------------------------------------
>
> Key: HIVE-25420
> URL: https://issues.apache.org/jira/browse/HIVE-25420
> Project: Hive
> Issue Type: Bug
> Reporter: Ádám Szita
> Assignee: Ádám Szita
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Time is a valid type in Iceberg but not in Hive. In Hive it is represented as a string type column, while (at least if ORC is used as underlying file format) long type is written out to data files.
> This requires translation two times: long@ORC -> LocalDate@Iceberg -> toString()@Hive and it works well for non vectorized reads, but when vectorization is turned on, we will get:
> {code:java}
> org.apache.hadoop.hive.ql.exec.vector.BytesColumnVector cannot be cast to org.apache.hadoop.hive.ql.exec.vector.LongColumnVector {code}
> Thus for now, time type is not supported with vectorization, and the relevant test cases should be ignored in such test configs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)