You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Prasanth Jayachandran (JIRA)" <ji...@apache.org> on 2018/02/01 03:00:02 UTC

[jira] [Updated] (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:all-tabpanel ]

Prasanth Jayachandran updated HIVE-15631:
-----------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0
           Status: Resolved  (was: Patch Available)

Test failures are unrelated. Committed patch to master!
Thanks [~tartarus] for the contribution!

> 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
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0
>
>         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
(v7.6.3#76005)