[
https://issues.apache.org/jira/browse/HIVE-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665148#action_12665148
]
Suresh Antony commented on HIVE-176:
------------------------------------
Changed hive.joblog.location to hive.querylog.location
Also changed e.PrintStacktrace()
Changed CliDriver.. Moved SessionState.start() after conf variable
initialization. Otherwise conf setting to change hive.querylog.location was
having no effect. Since HiveHistory was getting initialized even before
hiveconf was parsed.
Thanks for all the feedbacks.
> 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, patch_176.txt,
> patch_176.txt, patch_176.txt
>
>
> Josh <[email protected]> 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.
