hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joydeep Sen Sarma (JIRA)" <>
Subject [jira] Commented: (HIVE-176) structured log for obtaining query stats/info
Date Sat, 17 Jan 2009 08:51:59 GMT


Joydeep Sen Sarma commented on HIVE-176:

looks good for most part. let's get this committed!

would be happier if we renamed hive.joblog.location to hive.querylog.location. as for disabling
history - it seems that an invalid/blank location would effectively do that already.

error messages: if history file throws an filenotfoundexception - please go through console.printError
(instead of printStackTrace()) and give some message to user.

QTestUtil and TestCliDriver changes look good to me.

> structured log for obtaining query stats/info
> ---------------------------------------------
>                 Key: HIVE-176
>                 URL:
>             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
> Josh <> 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.

View raw message