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

stephen sprague commented on HIVE-14525:
----------------------------------------

ok.  lemme back up for a sec.

would people agree with me that stdout is reserved for *results* and stderr is 
where everything else goes? like info, debug, errors and warnings and anything 
else that comes up?  This is especially relevant for csv and tsv style output 
(machine readable.) for pretty output with ascii art around the results (human 
readable) it isn't quite as critical.

i'm curious if there is disagreement here.

for context i'd like to create a tsv file and i'd like to use beeline. :)    i 
suppose the de-facto method would be to use insert overwrite [local] directory 
and rsync the thing back to the cient - but i was hoping i could do it all 
through beeline.


> 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)

Reply via email to