Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Mon, 17 Nov 2014 20:21:35 +0000 (UTC)
From: "Eugene Koifman (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12755534.1416010695000.517621.1416255695276@Atlassian.JIRA>
In-Reply-To: <JIRA.12755534.1416010695000@Atlassian.JIRA>
References: <JIRA.12755534.1416010695000@Atlassian.JIRA>
 <JIRA.12755534.1416010695913@arcas>
Subject: [jira] [Updated] (HIVE-8881) Receiving json "{"error":"Could not
 find job job_1415748506143_0002"}" when web client tries to fetch all jobs
 from webhcat where HDFS does not have the data.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-8881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eugene Koifman updated HIVE-8881:
---------------------------------
    Status: Patch Available  (was: Open)

> Receiving json "{"error":"Could not find job job_1415748506143_0002"}" when web client tries to fetch all jobs from webhcat where HDFS does not have the data.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-8881
>                 URL: https://issues.apache.org/jira/browse/HIVE-8881
>             Project: Hive
>          Issue Type: Bug
>          Components: WebHCat
>    Affects Versions: 0.14.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>         Attachments: HIVE-8881.patch
>
>
> when a job is deleted from HDFS and the curl call is executed 
> http://localhost:50111/templeton/v1/jobs?user.name=hcat\&showall=true\&fields=*'
> Occasionally receiving json like this
> {noformat}
> {"error":"Could not find job job_1415748506143_0002"}
> {noformat}
> this is an intermittent issue that happens when Hadoop for some reason can't find the details for a given job id.
> This REST call should be more flexible since it is designed to return information about many jobs at once.  It should just skip over "bad" IDs and produce as much output as it can.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)