[ https://issues.apache.org/jira/browse/HIVE-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734346#comment-13734346 ]
Hive QA commented on HIVE-4545: ------------------------------- {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/12596693/HIVE-4545.3.patch {color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 2773 tests executed *Failed tests:* {noformat} org.apache.hcatalog.mapreduce.TestSequenceFileReadWrite.testTextTableWriteReadMR org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_ppd_vc {noformat} Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/348/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/348/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: 2 tests failed {noformat} This message is automatically generated. > HS2 should return describe table results without space padding > -------------------------------------------------------------- > > Key: HIVE-4545 > URL: https://issues.apache.org/jira/browse/HIVE-4545 > Project: Hive > Issue Type: Bug > Components: HiveServer2 > Reporter: Thejas M Nair > Assignee: Thejas M Nair > Attachments: HIVE-4545-1.patch, HIVE-4545.2.patch, HIVE-4545.3.patch > > > HIVE-3140 changed behavior of 'DESCRIBE table;' to be like 'DESCRIBE > FORMATTED table;'. HIVE-3140 introduced changes to not print header in > 'DESCRIBE table;'. But jdbc/odbc calls still get fields padded with space for > the 'DESCRIBE table;' query. > As the jdbc/odbc results are not for direct human consumption the space > padding should not be done for hive server2. -- 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