hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-12424) Make use of Kryo's Object-to-Object deep copy
Date Thu, 19 Nov 2015 23:31:11 GMT

    [ https://issues.apache.org/jira/browse/HIVE-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014748#comment-15014748
] 

Prasanth Jayachandran commented on HIVE-12424:
----------------------------------------------

Yes. It is blocked on Kryo. So far no response from kryo community. I think we won't be able
to target 2.0.0. If anything changes I will update this bug.

> Make use of Kryo's Object-to-Object deep copy
> ---------------------------------------------
>
>                 Key: HIVE-12424
>                 URL: https://issues.apache.org/jira/browse/HIVE-12424
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Serializers/Deserializers
>    Affects Versions: 2.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>
> Currently, plan serialization and operator tree serialization uses Object -> bytes
-> Object approach for deep copy. It also uses ByteArrayOutputStream as intermediate buffer
whose write method is synchronized. Similarly read from ByteArrayInputStream is also synchronized.
Also Utilities.clonePlan() creates a new HiveConf object that scans through conf directories
and adds site.xml which is an expensive operation. All these can be avoided using Kryo's Object
-> Object deep copy. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message