[
https://issues.apache.org/jira/browse/HIVE-11579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703099#comment-14703099
]
Ferdinand Xu commented on HIVE-11579:
-------------------------------------
When initializing the session error output stream(server side) and beeline
error output stream(client side), they are both redirected to the standard
error output. When invoking beeline.error, it will output some msg to the
beeline error output stream. At the meantime, the server side will log this
error as well. It's a little bit confusing since they actually output the error
msg twice. Given an example, you trying to use `lss` which is invalid command,
the server side will throw an exception which is output to the session's error
output stream. When the client gets the exception, we will use the method
beeline.error to output this error again.
> Invoke the set command will close standard error output[beeline-cli]
> --------------------------------------------------------------------
>
> Key: HIVE-11579
> URL: https://issues.apache.org/jira/browse/HIVE-11579
> Project: Hive
> Issue Type: Sub-task
> Components: CLI
> Reporter: Ferdinand Xu
> Assignee: Ferdinand Xu
> Attachments: HIVE-11579-beeline-cli.patch,
> HIVE-11579.2-beeline-cli.patch
>
>
> We can easily reproduce the debug by the following steps:
> {code}
> hive> set system:xx=yy;
> hive> lss;
> hive>
> {code}
> The error output disappeared since the err outputstream is closed when
> closing the Hive statement.
> This bug occurred also in the upstream when using the embeded mode as the new
> CLI uses.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
