[
https://issues.apache.org/jira/browse/HIVE-24503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mahesh kumar behera updated HIVE-24503:
---------------------------------------
Description: Serialization/Deserialization of vectorized batch done at
VectorSerializeRow and VectorDeserializeRow does a type checking for each
column of each row. This becomes very costly when there are billions of rows to
read/write. This can be optimized if the type check is done during init time
and specific reader/writer classes are created. This classes can be used
directly stored in filed structure to avoid run time type check. (was:
Serialization/Deserialization of vectorized batch done at VectorSerializeRow
and VectorDeserializeRow does a type checking for each column of each row. This
becomes very costly when there are billions of rows to read/write. This can be
optimized if the type check is done during init time and specific reader/writer
classes are created. )
> Optimize vector row serde by avoiding type check at run time
> -------------------------------------------------------------
>
> Key: HIVE-24503
> URL: https://issues.apache.org/jira/browse/HIVE-24503
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Reporter: mahesh kumar behera
> Assignee: mahesh kumar behera
> Priority: Major
>
> Serialization/Deserialization of vectorized batch done at VectorSerializeRow
> and VectorDeserializeRow does a type checking for each column of each row.
> This becomes very costly when there are billions of rows to read/write. This
> can be optimized if the type check is done during init time and specific
> reader/writer classes are created. This classes can be used directly stored
> in filed structure to avoid run time type check.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
