[
https://issues.apache.org/jira/browse/HIVE-10202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395538#comment-14395538
]
Hive QA commented on HIVE-10202:
--------------------------------
{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/12709285/HIVE-10202.patch
{color:red}ERROR:{color} -1 due to 5 failed/errored test(s), 8694 tests executed
*Failed tests:*
{noformat}
TestMinimrCliDriver-smb_mapjoin_8.q - did not produce a TEST-*.xml file
TestThriftHttpCLIService - did not produce a TEST-*.xml file
org.apache.hadoop.hive.thrift.TestHadoop20SAuthBridge.testMetastoreProxyUser
org.apache.hadoop.hive.thrift.TestHadoop20SAuthBridge.testSaslWithHiveMetaStore
org.apache.hive.jdbc.TestSSL.testSSLFetchHttp
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3278/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3278/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-3278/
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: 5 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12709285 - PreCommit-HIVE-TRUNK-Build
> Beeline outputs prompt+query on standard output when used in non-interactive
> mode
> ---------------------------------------------------------------------------------
>
> Key: HIVE-10202
> URL: https://issues.apache.org/jira/browse/HIVE-10202
> Project: Hive
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Sergio Peña
> Assignee: Naveen Gangam
> Fix For: 1.2.0
>
> Attachments: HIVE-10202.patch
>
>
> When passing a SQL script file to Hive CLI, the prompt+query is not sent to
> the standard output nor standard error. This is totally fine because users
> might want to send only the query results to the standard output, and parse
> the results from it.
> In the case of BeeLine, the promp+query is sent to the standard output
> causing extra parsing on the user scripts to avoid reading the prompt+query.
> Another drawback is in the security side. Sensitive queries are logged
> directly to the files where the standard output is redirected.
> How to reproduce:
> {noformat}
> $ cat /tmp/query.sql
> select *
> from test
> limit 1;
> $ beeline --showheader=false --outputformat=tsv2 -u
> jdbc:hive2://localhost:10000 -f /tmp/query.sql > /tmp/output.log 2>
> /tmp/error.log
> $ cat /tmp/output.log
> 0: jdbc:hive2://localhost:10000> select *
> . . . . . . . . . . . . . . . .> from test
> . . . . . . . . . . . . . . . .> limit 1;
> 451 451.713 false y2dh7 ["866","528","936"]
> 0: jdbc:hive2://localhost:10000>
> {noformat}
> We should avoid sending the prompt+query to the standard output/error
> whenever a script file is passed to BeeLine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
