Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B8BC617D00 for ; Thu, 2 Oct 2014 01:54:58 +0000 (UTC) Received: (qmail 40567 invoked by uid 500); 2 Oct 2014 01:54:58 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 40412 invoked by uid 500); 2 Oct 2014 01:54:58 -0000 Mailing-List: contact dev-help@falcon.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.incubator.apache.org Delivered-To: mailing list dev@falcon.incubator.apache.org Received: (qmail 40394 invoked by uid 99); 2 Oct 2014 01:54:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Oct 2014 01:54:58 +0000 X-ASF-Spam-Status: No, hits=-2000.6 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 02 Oct 2014 01:54:36 +0000 Received: (qmail 40197 invoked by uid 99); 2 Oct 2014 01:54:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Oct 2014 01:54:34 +0000 Date: Thu, 2 Oct 2014 01:54:34 +0000 (UTC) From: "Srikanth Sundarrajan (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (FALCON-510) Inject falcon related properties to job conf MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/FALCON-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14155986#comment-14155986 ] Srikanth Sundarrajan edited comment on FALCON-510 at 10/2/14 1:54 AM: ---------------------------------------------------------------------- [~peeyushb], We ought to add it in such a way that this would work for actions in user workflow as well as the pig scripts or hive launched from within user workflow actions. Would urge you to look at this specific [oozie feature|http://archive.cloudera.com/cdh4/cdh/4/oozie/WorkflowFunctionalSpec.html#a19_Global_Configurations] to enable this. was (Author: sriksun): [~peeyushb], We ought to add it in such a way that this work for actions in user workflow as well as the pig scripts or hive launched from within user workflow actions. Would urge you to look at this specific [oozie feature|http://archive.cloudera.com/cdh4/cdh/4/oozie/WorkflowFunctionalSpec.html#a19_Global_Configurations] to enable this. > Inject falcon related properties to job conf > -------------------------------------------- > > Key: FALCON-510 > URL: https://issues.apache.org/jira/browse/FALCON-510 > Project: Falcon > Issue Type: Improvement > Reporter: Shwetha G S > Assignee: Peeyush Bishnoi > Attachments: falcon-510.txt > > > Currently there is no falcon context injected at MR job level. The job conf has at most the oozie workflow / action ID either in the job name or sometimes in the job conf. > Therefore there is no way for a tool like hraven, which relies completely on jobconf and job history data, to identify that a particular job maps to a particular falcon process or it's instance time, etc. Right now hraven does regex-based job name surgery on a best effort basis before emitting metrics to graphite > Request the following feature in falcon: > Add the following properties to the job conf (for all jobs - be it a pig action or an MR action): > falcon.process.name > falcon.process.instancetime > while we're at it, might as well add any other falcon context as a jobconf property (like whether it was a rerun or the input/output feeds, cluster, validity, any process properties, etc.) > This will ofcourse inject at the first job level and cannot ensure that any child jobs get the properties passed on (unless we can figure out a way to do that too). -- This message was sent by Atlassian JIRA (v6.3.4#6332)