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 1E63517A5D for ; Fri, 17 Jul 2015 09:19:06 +0000 (UTC) Received: (qmail 40961 invoked by uid 500); 17 Jul 2015 09:19:06 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 40912 invoked by uid 500); 17 Jul 2015 09:19:06 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 40900 invoked by uid 99); 17 Jul 2015 09:19:05 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jul 2015 09:19:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 9262C18580C for ; Fri, 17 Jul 2015 09:19:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.97 X-Spam-Level: X-Spam-Status: No, score=0.97 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 8M0cP9P7A6CY for ; Fri, 17 Jul 2015 09:19:05 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id C752620EFB for ; Fri, 17 Jul 2015 09:19:04 +0000 (UTC) Received: (qmail 40897 invoked by uid 99); 17 Jul 2015 09:19:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jul 2015 09:19:04 +0000 Date: Fri, 17 Jul 2015 09:19:04 +0000 (UTC) From: "Pallavi Rao (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-1313) Generate notification for Falcon job status MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FALCON-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631080#comment-14631080 ] Pallavi Rao commented on FALCON-1313: ------------------------------------- [~peeyushb], the primary problem with any notification from Falcon is that it will not be reliable. Users would generally want to know when there are failures (rather than success). And, in case of failures, the notification may not get generated at all (either via oozie) or for that matter via JMS notifications. If you add the email notification as part of post-process, the user action may succeed, but, post-process may fail. If you listen to JMS notifications that are generated now, even there, JMS notifications may not generated because the post-processing failed. So, at best, what we are guaranteeing is SUCCESS notifications in case of "Success" which can be achieved using oozie email action. But, lack of notification, MAY, but not necessarily (when post-processing fails), mean a failure. I think we need to be able to reliably determine the status of a workflow/action before we bring in this feature. > Generate notification for Falcon job status > ------------------------------------------- > > Key: FALCON-1313 > URL: https://issues.apache.org/jira/browse/FALCON-1313 > Project: Falcon > Issue Type: New Feature > Components: common > Affects Versions: 0.6.1 > Reporter: Peeyush Bishnoi > Assignee: Peeyush Bishnoi > > Falcon should generate Email based notification for job status to the user/group when job finish either with success/failure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)