[jira] [Commented] (HIVE-14525) beeline still writing log data to stdout as of version 2.1.0

["Miklos Csanady (JIRA)" <ji...@apache.org>]

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

Miklos Csanady commented on HIVE-14525:
---------------------------------------

The "loggy kind of lines" contains the query, which is the subject of the other issue.

> beeline still writing log data to stdout as of version 2.1.0
> ------------------------------------------------------------
>
>                 Key: HIVE-14525
>                 URL: https://issues.apache.org/jira/browse/HIVE-14525
>             Project: Hive
>          Issue Type: Bug
>          Components: Beeline
>    Affects Versions: 2.1.0
>            Reporter: stephen sprague
>
> simple test. note that i'm looking to get a tsv file back.
> {code}
> $ beeline -u dwrdevnn1 --showHeader=false --outputformat=tsv2 <<SQL >stdout 2>stderr
> > select count(*)
> > from default.dual;
> > SQL
> {code}
> instead i get this in stdout:
> {code}
> $ cat stdout
> 0: jdbc:hive2://dwrdevnn1.sv2.trulia.com:1000> select count(*)
> . . . . . . . . . . . . . . . . . . . . . . .> from default.dual;
> 0
> 0: jdbc:hive2://dwrdevnn1.sv2.trulia.com:1000> 
> {code}
> i should only get one row which is the *result* of the query (which is 0) - not the ovthe loggy kind of lines you see above. that stuff goes to stderr my friends.
> also i refer to this ticket b/c the last comment suggested so - its close but not exactly the same.
> https://issues.apache.org/jira/browse/HIVE-14183



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)