[jira] Commented: (HIVE-176) structured log for obtaining query stats/info

["Suresh Antony (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660868#action_12660868 ] 

Suresh Antony commented on HIVE-176:
------------------------------------

attached a patch with following changes:
1.  HiveHistory stored in sessionState variable.  HiveHistory is created  on the first call to job log history. 
2. Removed all references to HiveHistory from CliDriver
3. Added a new config variable "hive.joblog.location" for the location of history file.  Not using scratch directory as the  default location because We are removing scratch directory at the end  of run. 

> structured log for obtaining query stats/info
> ---------------------------------------------
>
>                 Key: HIVE-176
>                 URL: https://issues.apache.org/jira/browse/HIVE-176
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 0.2.0
>            Reporter: Joydeep Sen Sarma
>            Assignee: Suresh Antony
>             Fix For: 0.2.0
>
>         Attachments: patch_176.txt, patch_176.txt
>
>
> Josh <jo...@besquared.net> wrote:
> When launching off hive queries using hive -e is there a way to get the job id so that I can just queue them up and go check their statuses later? What's the general pattern for queueing and monitoring without using the libraries directly?
> I'm gonna throw my vote in for a structured log format. Users could tail it and use whatever queuing or monitoring they wish. It's also probably just a 30 minute project for someone already familiar with the code. I suggest ^A seperated key=value pairs per log line.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.