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

Hive QA commented on HIVE-6507:
-------------------------------



{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/12631113/HIVE-6507.patch

{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 5354 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_auto_sortmerge_join_16
org.apache.hive.beeline.TestSchemaTool.testSchemaInit
org.apache.hive.beeline.TestSchemaTool.testSchemaUpgrade
{noformat}

Test results: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1631/testReport
Console output: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1631/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 exited with: TestsFailedException: 3 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12631113

> OrcFile table property names are specified as strings
> -----------------------------------------------------
>
>                 Key: HIVE-6507
>                 URL: https://issues.apache.org/jira/browse/HIVE-6507
>             Project: Hive
>          Issue Type: Bug
>          Components: HCatalog, Serializers/Deserializers
>    Affects Versions: 0.13.0
>            Reporter: Sushanth Sowmyan
>            Assignee: Sushanth Sowmyan
>         Attachments: HIVE-6507.2.patch, HIVE-6507.patch
>
>
> In HIVE-5504, we had to do some special casing in HCatalog to add a 
> particular set of orc table properties from table properties to job 
> properties.
> In doing so, it's obvious that that is a bit cumbersome, and ideally, the 
> list of all orc file table properties should really be an enum, rather than 
> individual loosely tied constant strings. If we were to clean this up, we can 
> clean up other code that references this to reference the entire enum, and 
> avoid future errors when new table properties are introduced, but other 
> referencing code is not updated.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to