You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Suresh Antony (JIRA)" <ji...@apache.org> on 2008/12/16 03:39:44 UTC
[jira] Commented: (HIVE-176) structured log for obtaining query
stats/info
[ https://issues.apache.org/jira/browse/HIVE-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656855#action_12656855 ]
Suresh Antony commented on HIVE-176:
------------------------------------
Some thoughts about logging:
- Thinking of following the same format as hadoop logging for the jobs
- each query will have separate file. location of the file will be printed to stdout while running the query.
- Format of the entries in file will be of the following.
<ENTRY TYPE> id=value key1=value1 key2=value2 .....
- Different entry types can be:
-QueryStart
-QueryEnd
-QueryStepStart
-QueryStepEnd
-QueryStepProgress
> 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
> Reporter: Joydeep Sen Sarma
>
> 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.