[HIVE-26658] INT64 Parquet timestamps cannot be mapped to most Hive numeric types

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.0.0-alpha-1
• Fix Version/s: 4.0.0-beta-1
• Component/s: Parquet, Serializers/Deserializers
• Labels: backwards-compatibility pull-request-available
• Assignee: Stamatis Zampetakis
• Reporter: Stamatis Zampetakis
• Created: 21/Oct/22 13:42
• Updated: 15/Aug/23 06:33
• Resolved: 10/Jan/23 11:48

Description

When attempting to read a Parquet file with column of primitive type INT64 and logical type TIMESTAMP an error is raised when the Hive type is different from TIMESTAMP and BIGINT.

Consider a Parquet file (e.g., ts_file.parquet) with the following schema:

{
  "name": "eventtime",
  "type": ["null", {
    "type": "long",
    "logicalType": "timestamp-millis"
  }],
  "default": null
}

 
Mapping the column to a Hive numeric type among TINYINT, SMALLINT, INT, FLOAT, DOUBLE, DECIMAL, and trying to run a SELECT will give back an error.

The following snippet can be used to reproduce the problem.

CREATE TABLE ts_table (eventtime INT) STORED AS PARQUET;
LOAD DATA LOCAL INPATH 'ts_file.parquet' into table ts_table;
SELECT * FROM ts_table;

This is a regression caused by HIVE-21215. Although, HIVE-21215 allows to read INT64 types as Hive TIMESTAMP, which was not possible before, at the same time it broke the mapping to every other Hive numeric type. The problem was addressed selectively for BIGINT type very recently (HIVE-26612).

The primary goal of this ticket is to restore backward compatibility since these use-cases were working before HIVE-21215.

Issue Links

• Discovered while testing: HIVE-26612 INT64 Parquet timestamps cannot be read into BIGINT Hive type
• is caused by: HIVE-21215 Read Parquet INT64 timestamp
• links to: GitHub Pull Request #3698