[
https://issues.apache.org/jira/browse/HIVE-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602303#comment-14602303
]
Thejas M Nair commented on HIVE-11094:
--------------------------------------
[~jcamachorodriguez] I am not able to reproduce this behavior. I tried with
1.2.1 RC0 as well as build from master.
{noformat}
./bin/beeline -u jdbc:hive2:// -e "show databases" > exec.out
Picked up JAVA_TOOL_OPTIONS: -Djava.awt.headless=true
Picked up JAVA_TOOL_OPTIONS: -Djava.awt.headless=true
Connecting to jdbc:hive2://
15/06/25 19:34:41 [main]: WARN util.NativeCodeLoader: Unable to load
native-hadoop library for your platform... using builtin-java classes where
applicable
15/06/25 19:34:46 [main]: WARN metastore.ObjectStore: Version information not
found in metastore. hive.metastore.schema.verification is not enabled so
recording the schema version 2.0.0
15/06/25 19:34:46 [main]: WARN metastore.ObjectStore: Failed to get database
default, returning NoSuchObjectException
Connected to: Apache Hive (version 2.0.0-SNAPSHOT)
Driver: Hive JDBC (version 2.0.0-SNAPSHOT)
Transaction isolation: TRANSACTION_REPEATABLE_READ
OK
1 row selected (3.065 seconds)
Beeline version 2.0.0-SNAPSHOT by Apache Hive
Closing: 0: jdbc:hive2://
134134[apache-hive-2.0.0-SNAPSHOT-bin19:34]$ cat exec.out
+----------------+--+
| database_name |
+----------------+--+
| default |
+----------------+--+
{noformat}
> Beeline redirecting all output to ErrorStream
> ---------------------------------------------
>
> Key: HIVE-11094
> URL: https://issues.apache.org/jira/browse/HIVE-11094
> Project: Hive
> Issue Type: Bug
> Components: CLI
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Attachments: HIVE-11094.patch
>
>
> Beeline is sending all output to ErrorStream, instead of using OutputStream
> for info or debug information.
> The problem can be reproduced by running:
> {noformat}
> ./bin/beeline -u jdbc:hive2:// -e "show databases" > exec.out
> {noformat}
> I will still print the output through the terminal. The reason seems to be
> that the normal output is also sent through the ErrorStream.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
