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

Hive QA commented on HIVE-5380:
-------------------------------



{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/12605396/HIVE-5380.patch

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 3176 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_bucket_num_reducers
{noformat}

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/934/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/934/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: 1 tests failed
{noformat}

This message is automatically generated.
                
> Non-default OI constructors should be supported if for backwards compatibility
> ------------------------------------------------------------------------------
>
>                 Key: HIVE-5380
>                 URL: https://issues.apache.org/jira/browse/HIVE-5380
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.13.0
>            Reporter: Brock Noland
>            Assignee: Brock Noland
>            Priority: Minor
>         Attachments: HIVE-5380.patch
>
>
> In HIVE-5263 we started serializing OI's when cloning the plan. This was a 
> great boost in speed for many queries. In the future we'd like to stop 
> copying the OI's, perhaps in HIVE-4396.
> Until then Custom Serdes will not work on trunk. This is a fix to allow 
> custom serdes such as the Hive JSon Serde work until we address the fact we 
> don't want to have to copy the OI's.

--
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

Reply via email to