[
https://issues.apache.org/jira/browse/HIVE-11209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639235#comment-14639235
]
Prasanth Jayachandran commented on HIVE-11209:
----------------------------------------------
I just checked that this is not a problem for vectorized version which does not
call setFromBytes, this will only impact the non-vectorized code path.
Non-vectorized code path already does many allocations for HiveDecimal and so
shouldn't be noticeable. +1
> Clean up dependencies in HiveDecimalWritable
> --------------------------------------------
>
> Key: HIVE-11209
> URL: https://issues.apache.org/jira/browse/HIVE-11209
> Project: Hive
> Issue Type: Sub-task
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 2.0.0
>
> Attachments: HIVE-11209.patch, HIVE-11209.patch, HIVE-11209.patch,
> HIVE-11209.patch
>
>
> Currently HiveDecimalWritable depends on:
> * org.apache.hadoop.hive.serde2.ByteStream
> * org.apache.hadoop.hive.serde2.lazybinary.LazyBinaryUtils
> * org.apache.hadoop.hive.serde2.typeinfo.HiveDecimalUtils
> since we need HiveDecimalWritable for the decimal VectorizedColumnBatch,
> breaking these dependencies will improve things.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
