hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <>
Subject [jira] [Commented] (HIVE-6307) "completed" field description should be clarified.
Date Wed, 05 Feb 2014 06:40:09 GMT


Lefty Leverenz commented on HIVE-6307:

Thanks for the clarification, [~eugene.koifman].  Please review this new description:

.bq  A string representing completed status of the process launched by the Launcher task.
For example when a MapReduce job is submitted via WebHCat, the Launcher invokes a "hadoop
jar" command and then when that process exits the completed string is set to "done". Note
that this is not the same as the job status (see status).

It's got a run-on sentence that could use further tweaking.  Here's the link with full formatting:

* [GET jobs/:jobid Results |]

> "completed" field description should be clarified.
> --------------------------------------------------
>                 Key: HIVE-6307
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Documentation, WebHCat
>    Affects Versions: 0.12.0
>            Reporter: Eugene Koifman
>            Assignee: Lefty Leverenz
> explains the fields
in the JSON document which contains status information for a particular job.
> "completed" field is set once the process that the Launcher task launched returns.  For
example, if user submitted a M/R job via webhcat, "completed" will be set to "done" once the
"hadoop jar" command that the Launcher invokes exits.  If one is looking for status of the
job itself, the fields inside "status" element should be consulted (e.g. "jobComplete" or
> Current doc is not clear and may mislead WebHCat user into thinking "completed" is a
property of the job itself.

This message was sent by Atlassian JIRA

View raw message