[
https://issues.apache.org/jira/browse/HIVE-7022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-7022:
------------------------------
Description:
Currently ParquetHiveSerde uses BinaryWritable to enclose bytes read from
Parquet data. However, existing Hadoop class, BytesWritable, already does that,
and BinaryWritable offers no advantage. On the other hand, BinaryWritable has a
confusing getString() method, which, if misused, can cause unexpected result.
The proposal here is to replace it with Hadoop BytesWritable.
The issue was identified in HIVE-6367, serving as a follow-up JIRA.
was:
Currently ParquetHiveSerde uses BinaryWritable to enclose bytes read from
Parquet data. However, existing Hadoop class, BytesWritable, already does that,
and BinaryWritable offers no advantage. On the other hand, BinaryWritable has a
confusing getString() method, which, in misused, can cause unexpected result.
The proposal here is to replace it with Hadoop BytesWritable.
The issue was identified in HIVE-6367, serving as a follow-up JIRA.
> Replace BinaryWritable with BytesWritable in Parquet serde
> ----------------------------------------------------------
>
> Key: HIVE-7022
> URL: https://issues.apache.org/jira/browse/HIVE-7022
> Project: Hive
> Issue Type: Improvement
> Components: Serializers/Deserializers
> Affects Versions: 0.13.0
> Reporter: Xuefu Zhang
> Assignee: Xuefu Zhang
> Attachments: HIVE-7022.patch
>
>
> Currently ParquetHiveSerde uses BinaryWritable to enclose bytes read from
> Parquet data. However, existing Hadoop class, BytesWritable, already does
> that, and BinaryWritable offers no advantage. On the other hand,
> BinaryWritable has a confusing getString() method, which, if misused, can
> cause unexpected result. The proposal here is to replace it with Hadoop
> BytesWritable.
> The issue was identified in HIVE-6367, serving as a follow-up JIRA.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
