[
https://issues.apache.org/jira/browse/HIVE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759196#comment-13759196
]
Mohammad Kamrul Islam commented on HIVE-1511:
---------------------------------------------
For some test cases (such as input16.q), Kryo failed to find the class.
Although the jar is already in its class path. I debugged into Kryo and found
it uses getClass().getClassLoader(). I changed it to getContextClassLoader()
and it resolved the issue. In this respect, should we ask kayo to change its
code? or we need to make sure the jar should be available through
getClassLoader().
I made the following code change at line 105 of
src/com/esotericsoftware/kryo/Kryo.java
- private ClassLoader classLoader = getClass().getClassLoader();
+ private ClassLoader classLoader =
Thread.currentThread().getContextClassLoader();
> 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, 0.11.0
> Reporter: Ning Zhang
> Assignee: Mohammad Kamrul Islam
> Attachments: failedPlan.xml, generated_plan.xml, HIVE-1511.10.patch,
> HIVE-1511.11.patch, HIVE-1511.4.patch, HIVE-1511.5.patch, HIVE-1511.6.patch,
> HIVE-1511.7.patch, HIVE-1511.8.patch, HIVE-1511.9.patch, HIVE-1511.patch,
> HIVE-1511-wip2.patch, HIVE-1511-wip3.patch, HIVE-1511-wip4.patch,
> HIVE-1511.wip.9.patch, HIVE-1511-wip.patch, KryoHiveTest.java, run.sh
>
>
> 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
