hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-14389) Beeline should not output query and prompt to stdout
Date Thu, 11 May 2017 09:23:04 GMT

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

Hive QA commented on HIVE-14389:
--------------------------------



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

{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 10682 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[vector_join30] (batchId=149)
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_3] (batchId=97)
org.apache.hive.beeline.TestBeeLineWithArgs.testTabInScriptFile (batchId=219)
{noformat}

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
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: 12867465 - PreCommit-HIVE-Build

> Beeline should not output query and prompt to stdout
> ----------------------------------------------------
>
>                 Key: HIVE-14389
>                 URL: https://issues.apache.org/jira/browse/HIVE-14389
>             Project: Hive
>          Issue Type: Improvement
>          Components: Beeline
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Minor
>         Attachments: HIVE-14389.01.patch, HIVE-14389.02.patch, HIVE-14389.03.patch
>
>
> It seems that the Beeline prints the query along with the results in the stdout when
a script file is passed. The output file in the example below needs to only have the results
and not the query.
> {noformat}
> .vihang-MBP:bin vihang$ ./beeline --showheader=false --outformat=tsv2 -u "jdbc:hive2://localhost:10000"
-f /tmp/query.sql > /tmp/query.out 2> /tmp/query.err
> OK
> $ cat /tmp/query.out
> 1: jdbc:hive2://localhost:10000/default> select * from likes limit 4;
> +-----------+--------------+--+
> | 1         | chocolate    |
> | 1         | car          |
> | 1         | games        |
> | 1         | chess        |
> +-----------+--------------+--+
> 1: jdbc:hive2://localhost:10000/default>
> 1: jdbc:hive2://localhost:10000/default>
> $
> {noformat}
> A lot of people use HiveCLI and in order to transition from HiveCLI scripts to Beeline,
this needs to be taken care of. The output files generated by beeline should contain only
the results and nothing else.
> Similarly, when not in silent mode, query are being printed out on stdout, which is adding
garbage along with results, as just like HIVE CLI does, users would like to have only the
results on stdout, not errors/debugging info/etc, like the full query. 
> Query could be printed out, no problem, as long as it is not on stdout (with results),
instead, it must be printed out along with the debugging info.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message