You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Venkatesh Seetharam (JIRA)" <ji...@apache.org> on 2014/11/13 04:34:31 UTC

[jira] [Commented] (FALCON-780) PrismFeedSnSTest assumes synchronous oozie operation

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

Venkatesh Seetharam commented on FALCON-780:
--------------------------------------------

Moving this out of 0.6. Please provide a patch if this needs to get into 0.6.

> PrismFeedSnSTest assumes synchronous oozie operation
> ----------------------------------------------------
>
>                 Key: FALCON-780
>                 URL: https://issues.apache.org/jira/browse/FALCON-780
>             Project: Falcon
>          Issue Type: Bug
>          Components: merlin
>    Affects Versions: 0.6
>            Reporter: Raghav Kumar Gautam
>            Assignee: Raghav Kumar Gautam
>         Attachments: falcon-780.diff
>
>
> In the PrismFeedSnSTest the code assumes synchronous oozie operations:
> {code}
>         bundles[0].submitAndScheduleFeed();
>         TimeUtil.sleepSeconds(TIMEOUT);
>         AssertUtil.checkStatus(cluster1OC, EntityType.FEED, bundles[0], Job.Status.RUNNING);
>         AssertUtil.checkNotStatus(cluster1OC, EntityType.PROCESS, bundles[1], Job.Status.RUNNING);
> {code}
> Since, oozie operations are asnchronous, we need to allow some delay between between operation and the time when its effects are visible.



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