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

Hive QA commented on HIVE-19767:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12926129/HIVE-19767.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 14463 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[vectorization_decimal_date]
 (batchId=84)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[windowing_columnPruning] 
(batchId=84)
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/11523/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/11523/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-11523/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12926129 - PreCommit-HIVE-Build

> HiveServer2 should take hiveconf for non Hive properties
> --------------------------------------------------------
>
>                 Key: HIVE-19767
>                 URL: https://issues.apache.org/jira/browse/HIVE-19767
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 1.2.2, 3.0.0, 2.3.2
>            Reporter: Szehon Ho
>            Assignee: Szehon Ho
>            Priority: Major
>         Attachments: HIVE-19767.patch
>
>
> The -hiveconf command line option works in HiveServer2 with properties in 
> HiveConf.java, but not so well with other properties (like mapred properties 
> or spark properties to control underlying execution engine, or custom 
> properties understood by custom listeners)
> It is inconsistent with HiveCLI.
> HiveCLI behavior:
> {noformat}
> ./bin/hive --hiveconf a=b
> hive> set a;
> a=b {noformat}
> HiveServer2 behavior:
> {noformat}
> ./bin/hiveserver2 --hiveconf a=b
> beeline> set a;
> +-----------------+
> |       set       |
> +-----------------+
> | a is undefined  |
> +-----------------+{noformat}
> Although it is possible to set up hive-site.xml or even mapred-site.xml to 
> fill in the relevant properties, it is more convenient when testing HS2 with 
> different configuration to be able to use --hiveconf to change on the fly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to