You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Ashutosh Chauhan (JIRA)" <ji...@apache.org> on 2017/11/16 20:34:00 UTC
[jira] [Commented] (HIVE-15631) Optimize for hive client logs , you
can filter the log for each session itself.
[ https://issues.apache.org/jira/browse/HIVE-15631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255921#comment-16255921 ]
Ashutosh Chauhan commented on HIVE-15631:
-----------------------------------------
[~prasanth_j] [~thejas] this seems pretty useful for debugging.
> Optimize for hive client logs , you can filter the log for each session itself.
> -------------------------------------------------------------------------------
>
> Key: HIVE-15631
> URL: https://issues.apache.org/jira/browse/HIVE-15631
> Project: Hive
> Issue Type: Improvement
> Components: CLI, Clients, Hive
> Reporter: tartarus
> Assignee: tartarus
> Attachments: HIVE_15631.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> We have several hadoop cluster, about 15 thousand nodes. Every day we use hive to submit above 100 thousand jobs.
> So we have a large file of hive logs on every client host every day, but i don not know the logs of my session submitted was which line.
> So i hope to print the hive.session.id on every line of logs, and then i could use grep to find the logs of my session submitted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)