[
https://issues.apache.org/jira/browse/HIVE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739810#comment-13739810
]
Leo Romanoff commented on HIVE-1511:
------------------------------------
@Ashutosh: I tried out your latest patch. My results and conclusions are:
1) auto_sortmerge_join-*.q failure: it seems like copyMRWork method still uses
XML serializer instead of Kryo based on the stacktrace of exception that I get
2) bucketcontext_*.q fails because it seems to produce wrong numeric results.
And test compares expected number to the one delivered by the test run. So, it
seems to be a semantic error, not a usual exception during (de)serialization.
3) I tried randomly some of smb_mapjoin_*.q tests. All of them seem to finish
successfully.
Regarding reporting problems: It would be nice if reports would provide
exceptions with stacktraces and may be other information that could be useful
to identify real problems. It helps a lot.
-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.patch, HIVE-1511-wip2.patch,
> HIVE-1511-wip3.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
