[
https://issues.apache.org/jira/browse/PARQUET-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viacheslav Shalamov updated PARQUET-1718:
-----------------------------------------
Description:
When writing a POJO with `short` field, it ends up in parquet file as 32-bit
int because of:
??16-bit ints are not explicitly supported in the storage format since they are
covered by 32-bit ints with an efficient encoding.??
[https://github.com/apache/parquet-format#types]
How about annotating it with logical type `IntType (bitWidth = 16, isSigned =
true)` ?
was:
When writing a POJO with `short` field, it ends up in parquet file as 32-bit
int because of:
> 16-bit ints are not explicitly supported in the storage format since they are
> covered by 32-bit ints with an efficient encoding.
[https://github.com/apache/parquet-format#types]
How about annotating it with logical type `IntType (bitWidth = 16, isSigned =
true)` ?
> Store int16 as int16
> --------------------
>
> Key: PARQUET-1718
> URL: https://issues.apache.org/jira/browse/PARQUET-1718
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-mr
> Reporter: Viacheslav Shalamov
> Priority: Major
>
> When writing a POJO with `short` field, it ends up in parquet file as 32-bit
> int because of:
> ??16-bit ints are not explicitly supported in the storage format since they
> are covered by 32-bit ints with an efficient encoding.??
> [https://github.com/apache/parquet-format#types]
>
> How about annotating it with logical type `IntType (bitWidth = 16, isSigned =
> true)` ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
