[
https://issues.apache.org/jira/browse/HIVE-16061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890274#comment-15890274
]
Aihua Xu commented on HIVE-16061:
---------------------------------
[~muxin] Thanks for the info. Your analysis makes sense and the direction looks
good. Seems we are not printing some info to OperationLog so the client can't
query it.
Seems you are focusing on a different part of logging in JobDebugger. I tried
your patch, seems it's still not printing MR progress.
{noformat}
0: jdbc:hive2://localhost:10000> select t1.key from src t1 join src t2 on
t1.key=t2.key limit 10;
WARNING: Hive-on-MR is deprecated in Hive 2 and may not be available in the
future versions. Consider using a different execution engine (i.e. tez, spark)
or using Hive 1.X releases.
+---------+
| t1.key |
+---------+
| 0 |
| 10 |
+---------+
{noformat}
> Some of console output is not printed to the beeline console
> ------------------------------------------------------------
>
> Key: HIVE-16061
> URL: https://issues.apache.org/jira/browse/HIVE-16061
> Project: Hive
> Issue Type: Bug
> Components: Logging
> Affects Versions: 2.1.1
> Reporter: Aihua Xu
> Assignee: Aihua Xu
>
> Run a hiveserver2 instance "hive --service hiveserver2".
> Then from another console, connect to hiveserver2 "beeline -u
> "jdbc:hive2://localhost:10000"
> When you run a MR job like "select t1.key from src t1 join src t2 on
> t1.key=t2.key", some of the console logs like MR job info are not printed to
> the console while it just print to the hiveserver2 console.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
