[
https://issues.apache.org/jira/browse/HIVE-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765142#comment-13765142
]
Hive QA commented on HIVE-5263:
-------------------------------
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12602678/HIVE-5263.patch
{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 3090 tests executed
*Failed tests:*
{noformat}
org.apache.hive.hcatalog.mapreduce.TestSequenceFileReadWrite.testSequenceTableWriteRead
org.apache.hive.hcatalog.mapreduce.TestSequenceFileReadWrite.testTextTableWriteRead
org.apache.hive.hcatalog.mapreduce.TestSequenceFileReadWrite.testSequenceTableWriteReadMR
org.apache.hive.hcatalog.mapreduce.TestSequenceFileReadWrite.testTextTableWriteReadMR
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/703/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/703/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests failed with: TestsFailedException: 4 tests failed
{noformat}
This message is automatically generated.
> Query Plan cloning time could be improved by using Kryo
> --------------------------------------------------------
>
> Key: HIVE-5263
> URL: https://issues.apache.org/jira/browse/HIVE-5263
> Project: Hive
> Issue Type: Improvement
> Reporter: Brock Noland
> Assignee: Brock Noland
> Attachments: HIVE-5263.patch, HIVE-5263.patch, HIVE-5263.patch
>
>
> In HIVE-1511 we implemented Kryo for serialization but did not use for query
> plan cloning. As was discussed there it's a possible speed improvement. In
> addition the current XML serialization method does not work with Java 7 so
> using Kryo is a workaround for this issue.
--
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
