[
https://issues.apache.org/jira/browse/HIVE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747338#comment-13747338
]
Leo Romanoff commented on HIVE-1511:
------------------------------------
@[~brocknoland] The problem with deserialization that you reported am 21 August
seems interesting. It could be an indication of a bug in Kryo. At the first
glance it looks as if there is a bug in serialization of strings or in
writing/reading object references. I'll look into it if time permits.
It would be very nice to get a reduced version of this test (e.g. only the data
structure that fails and the content of fields that leads to it), which can be
easily reproduced as a JUnit-test for Kryo.
-Leo
> Hive plan serialization is slow
> -------------------------------
>
> Key: HIVE-1511
> URL: https://issues.apache.org/jira/browse/HIVE-1511
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 0.7.0
> Reporter: Ning Zhang
> Assignee: Mohammad Kamrul Islam
> Attachments: HIVE-1511.4.patch, HIVE-1511.5.patch, HIVE-1511.6.patch,
> HIVE-1511.7.patch, HIVE-1511.8.patch, HIVE-1511.patch, HIVE-1511-wip2.patch,
> HIVE-1511-wip3.patch, HIVE-1511-wip4.patch, HIVE-1511-wip.patch
>
>
> As reported by Edward Capriolo:
> For reference I did this as a test case....
> SELECT * FROM src where
> key=0 OR key=0 OR key=0 OR key=0 OR key=0 OR key=0 OR key=0 OR key=0
> OR key=0 OR key=0 OR key=0 OR
> key=0 OR key=0 OR key=0 OR key=0 OR key=0 OR key=0 OR key=0 OR key=0
> OR key=0 OR key=0 OR key=0 OR
> ...(100 more of these)
> No OOM but I gave up after the test case did not go anywhere for about
> 2 minutes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
