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 099BB17874 for ; Fri, 17 Jul 2015 08:23:13 +0000 (UTC) Received: (qmail 34989 invoked by uid 500); 17 Jul 2015 08:23:06 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 34949 invoked by uid 500); 17 Jul 2015 08:23: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 34938 invoked by uid 99); 17 Jul 2015 08:23:06 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jul 2015 08:23:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 4A74CC0910 for ; Fri, 17 Jul 2015 08:23:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.77 X-Spam-Level: * X-Spam-Status: No, score=1.77 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, 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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id l-_8Z2dMUo2I for ; Fri, 17 Jul 2015 08:23: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 9606020F3F for ; Fri, 17 Jul 2015 08:23:05 +0000 (UTC) Received: (qmail 33926 invoked by uid 99); 17 Jul 2015 08:23:05 -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 08:23:05 +0000 Date: Fri, 17 Jul 2015 08:23:05 +0000 (UTC) From: "Peeyush Bishnoi (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=14630986#comment-14630986 ] Peeyush Bishnoi commented on FALCON-1313: ----------------------------------------- It depends on the type of use case and users for email notification to be useful. Through this issue, we are not mandating for email notification but we want to provide as an option to the users who feels it is useful and must be available. If you think that email notification should be kept in workflow (by leveraging Oozie email action) instead of inside Falcon that also looks fine. But want to know how users can add this functionality to the generated workflow of it's own if they submit entities from UI or CLI. > 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)