Altinity / Altinity/ice

Ice insert does not preserve logical datatype in parquet

Open
#70 1 comment 0 reactions 1 assignee View on GitHub

@subkanthi is already working on this.

Since Oct 30, 2025.

Dominant language
Java
Stars
35
Forks
7
Avg merge
5d 12h
Merged PRs (30d)
2

Description

After ice insert:

$ parquet-tools inspect ~/Desktop/1761746450566-169c87db783407235acfb0cb2f14bf1df2e5855df3a4e7a4b55bd64eecaeda9c.parquet 

############ file meta data ############
created_by: parquet-mr version 1.15.1 (build c7257b8faff5699e13bbc781679dc03f48c1102a)
num_columns: 2
num_rows: 1
num_row_groups: 1
format_version: 1.0
serialized_size: 489


############ Columns ############
year
data_col

############ Column(year) ############
name: year
path: year
max_definition_level: 0
max_repetition_level: 0
physical_type: INT32
logical_type: None
converted_type (legacy): NONE
compression: GZIP (space_saved: -74%)

############ Column(data_col) ############
name: data_col
path: data_col
max_definition_level: 0
max_repetition_level: 0
physical_type: INT32
logical_type: None
converted_type (legacy): NONE
compression: GZIP (space_saved: -74%)

Before:

$ parquet-tools inspect ~/Desktop/0_0_0_0_8DE63E1F13ABD6974B28FC2035C2D569.parquet 

############ file meta data ############
created_by: ClickHouse v25.8.9.20238.altinityantalya
num_columns: 2
num_rows: 2
num_row_groups: 1
format_version: 2.6
serialized_size: 263


############ Columns ############
year
data_col

############ Column(year) ############
name: year
path: year
max_definition_level: 0
max_repetition_level: 0
physical_type: INT32
logical_type: Int(bitWidth=16, isSigned=false)
converted_type (legacy): UINT_16
compression: ZSTD (space_saved: -60%)

############ Column(data_col) ############
name: data_col
path: data_col
max_definition_level: 0
max_repetition_level: 0
physical_type: INT32
logical_type: Int(bitWidth=8, isSigned=false)
converted_type (legacy): UINT_8
compression: ZSTD (space_saved: -56%)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.