Return-Path: 
 <dev-return-12968-apmail-falcon-dev-archive=falcon.apache.org@falcon.apache.org>
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 792C118B49
	for <apmail-falcon-dev-archive@minotaur.apache.org>;
 Tue,  7 Jul 2015 05:12:07 +0000 (UTC)
Received: (qmail 82761 invoked by uid 500); 7 Jul 2015 05:12:07 -0000
Delivered-To: apmail-falcon-dev-archive@falcon.apache.org
Received: (qmail 82720 invoked by uid 500); 7 Jul 2015 05:12:07 -0000
Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@falcon.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@falcon.apache.org>
List-Post: <mailto:dev@falcon.apache.org>
List-Id: <dev.falcon.apache.org>
Reply-To: dev@falcon.apache.org
Delivered-To: mailing list dev@falcon.apache.org
Received: (qmail 82709 invoked by uid 99); 7 Jul 2015 05:12:07 -0000
Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jul 2015 05:12:07 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org)
 with ESMTP id D7EE01A66ED
	for <dev@falcon.apache.org>; Tue,  7 Jul 2015 05:12:06 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd2-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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new,
 port 10024)
	with ESMTP id hpaR5lW8-Rvz for <dev@falcon.apache.org>;
	Tue,  7 Jul 2015 05:12:06 +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 1BAFC24962
	for <dev@falcon.incubator.apache.org>; Tue,  7 Jul 2015 05:12:06 +0000 (UTC)
Received: (qmail 82706 invoked by uid 99); 7 Jul 2015 05:12:05 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jul 2015 05:12:05 +0000
Date: Tue, 7 Jul 2015 05:12:05 +0000 (UTC)
From: "Pallavi Rao (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12775292.1424071054000.114377.1436245925909@Atlassian.JIRA>
In-Reply-To: <JIRA.12775292.1424071054000@Atlassian.JIRA>
References: <JIRA.12775292.1424071054000@Atlassian.JIRA>
 <JIRA.12775292.1424071054461@arcas>
Subject: [jira] [Commented] (FALCON-1031) Make post processing notifications
 to user topics optional
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-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616189#comment-14616189 ] 

Pallavi Rao commented on FALCON-1031:
-------------------------------------

Option of Commons Cli does not allow for '.' character in an arg.  It throws the below exception:
{code}
java.lang.IllegalArgumentException: opt contains illegal character value '.'
	at org.apache.commons.cli.OptionValidator.validateOption(OptionValidator.java:73)
	at org.apache.commons.cli.Option.<init>(Option.java:123)
	at org.apache.commons.cli.Option.<init>(Option.java:105)
	at org.apache.falcon.workflow.WorkflowExecutionArgs.getOption(WorkflowExecutionArgs.java:103)
{code}

'_' or '$' can be used. But, it won't seem like falcon system namespace. Changes to not use Option is a bigger change. Let me know if you would like me to proceed with '_' or '$'. Personally, I don't like either and would prefer to park this change (and other system properties) for later.

> Make post processing notifications to user topics optional
> ----------------------------------------------------------
>
>                 Key: FALCON-1031
>                 URL: https://issues.apache.org/jira/browse/FALCON-1031
>             Project: Falcon
>          Issue Type: Improvement
>    Affects Versions: 0.7
>            Reporter: Pallavi Rao
>            Assignee: Pallavi Rao
>            Priority: Minor
>              Labels: reviewed
>         Attachments: FALCON-1031-v2.patch, FALCON-1031-v3.patch, FALCON-1031.patch
>
>
> Currently, during post processing, messages are sent to Falcon system Topic and also to user topic (one per entity), by default. If the user is not interested in listening to job completion notifications, this is just additional load on the MQ.
> There should be an option to enable job completion notifications for users. To ensure backward compatibility, we should add to option to disable user notifications, may be, in the entity definition.



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