[
https://issues.apache.org/jira/browse/HIVE-19328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456131#comment-16456131
]
Peter Vary commented on HIVE-19328:
-----------------------------------
Some time ago I did extensive work on LogHelper (console), and wrote some
comments there. It might help to find out more details about how it currently
works:
[https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/session/SessionState.java#L1056]
{quote} * Logs info into the log file, and if not silent then into the
HiveServer2 or HiveCli info
* stream too. Handles an extra detail which will not be printed if null.
* BeeLine uses the operation log file to show the logs to the user, so
depending on the
* BeeLine settings it could be shown to the user.{quote}
> Some error messages like "table not found" are printing to STDERR
> -----------------------------------------------------------------
>
> Key: HIVE-19328
> URL: https://issues.apache.org/jira/browse/HIVE-19328
> Project: Hive
> Issue Type: Sub-task
> Components: Logging
> Affects Versions: 3.0.0
> Reporter: Aihua Xu
> Priority: Major
>
> In Driver class, we are printing the exceptions to the log file and to the
> console through LogHelper.
> https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/Driver.java#L730
> I can see the following exceptions in the stderr.
> FAILED: SemanticException [Error 10001]: Table not found default.sample_07
> If it's from HiveCli, that makes sense to print to console, while if it's
> beeline talking to HS2, then such log should go to HS2 log and beeline
> console. So we should differentiate these two scenarios.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)