Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Date: Thu, 3 Sep 2015 14:11:45 +0000 (UTC)
From: "Balu Vellanki (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12850084.1438206126000.247047.1441289505855@Atlassian.JIRA>
In-Reply-To: <JIRA.12850084.1438206126000@Atlassian.JIRA>
References: <JIRA.12850084.1438206126000@Atlassian.JIRA>
 <JIRA.12850084.1438206126247@arcas>
Subject: [jira] [Commented] (FALCON-1339) List feed entities shows scheduled
 Feed entities as submitted
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FALCON-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729114#comment-14729114 ] 

Balu Vellanki commented on FALCON-1339:
---------------------------------------

[~sriksun] : Completed is analogous to succeeded, so I agree that we should use completed instead for better readability. 

An entity bundle can be killed or the bundle itself can fail on the workflow engine. This is different from Instance failure. Showing the entity bundle status can alert the user to debug potential issues with the bundle. So I think it might be useful, isnt it?

> List feed entities shows scheduled Feed entities as submitted
> -------------------------------------------------------------
>
>                 Key: FALCON-1339
>                 URL: https://issues.apache.org/jira/browse/FALCON-1339
>             Project: Falcon
>          Issue Type: Bug
>    Affects Versions: 0.6.1
>            Reporter: Balu Vellanki
>            Assignee: Balu Vellanki
>            Priority: Critical
>
> To reproduce this issue, please do the following steps.
> - Submit a source cluster named primaryCluster.
> - Submit a feed.
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <feed name="rawEmailFeed" description="Raw customer email feed" xmlns="uri:falcon:feed:0.1">
>     <tags>externalSystem=USWestEmailServers</tags>
>     <groups>churnAnalysisDataPipeline</groups>
>     <frequency>hours(1)</frequency>
>     <timezone>UTC</timezone>
>     <late-arrival cut-off="hours(1)"/>
>     <clusters>
>         <cluster name="primaryCluster" type="source">
>             <validity start="2015-07-22T01:00Z" end="2015-07-22T03:00Z"/>
>             <retention limit="days(90)" action="delete"/>
>         </cluster>
>     </clusters>
>     <locations>
>         <location type="data" path="/user/ambari-qa/falcon/demo/primary/input/enron/${YEAR}-${MONTH}-${DAY}-${HOUR}"/>
>         <location type="stats" path="/"/>
>         <location type="meta" path="/"/>
>     </locations>
>     <ACL owner="ambari-qa" group="users" permission="0x755"/>
>     <schema location="/none" provider="/none"/>
> </feed>
> {code}
> - Schedule this feed.
> - A bundle is not created for this feed because,
> {code}
> "Feed Retention is not applicable as Feed's end time for cluster primaryCluster is not in the future"
> {code}
> Since there are no running bundles on the cluster, the status of this feed will always be shown as "SUBMITTED" even after being scheduled. 


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