[ https://issues.apache.org/jira/browse/FALCON-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492491#comment-14492491 ] Alex C commented on FALCON-1149: -------------------------------- Apologies - regarding my previous comment concerning the output feed location, I had forgot to also apply the workaround to the output feed instance; when I tested that, by specifying 'today(24,0)' instead of 'today(0,0)' on the output, I got the desired behaviour for the output written to feed f2. > The 'today' EL date expression is resolving to yesterday's date, for process instance input feed ranges > ------------------------------------------------------------------------------------------------------- > > Key: FALCON-1149 > URL: https://issues.apache.org/jira/browse/FALCON-1149 > Project: Falcon > Issue Type: Bug > Affects Versions: 0.5, 0.6 > Environment: HDP 2.1 sandbox, HDP 2.2 sandbox; server in UTC > Reporter: Alex C > Assignee: Ajay Yadava > > *Steps to reproduce* > 1. Submit a cluster named 'sandbox': > {code:xml} > > > > > > > > > > > > > > > {code} > 2. Submit a feed f1: > {code:xml} > > days(1) > UTC > > > > > > > > > path="/f1/${YEAR}/${MONTH}/${DAY}" /> > > > > > {code} > 3. Submit a process p1: > {code:xml} > > > > > > > 1 > FIFO > days(1) > > > > > > > > > {code} > 4. Submit a feed f2: > {code:xml} > > days(1) > UTC > > > > > > > > > path="/f2/${YEAR}/${MONTH}/${DAY}" /> > > > > > {code} > 5. Submit a process p2: > {code:xml} > > > > > > > 1 > FIFO > days(1) > > > > > > > > > > {code} > 6. Note that: > - Process p1 has no input feed (the data is fetched from some other location by p1). > - Feed f1 is referenced in the output of p1, and also referenced in the input of p2. > - All feeds are daily, and process input feed ranges and output feeds are daily, by way of the 'today(0,0)' EL expression. > 7. Finally, schedule all feeds and processes after 08:30Z on a given day, 'today'.. > *Expected:* > 1. The first scheduled instance for p1 proceeds to COMPLETED, and produces a partition in f1 for 'today' > 2. The first scheduled instance for p2 proceeds to COMPLETED, and produces a partition in f2 for 'today', since it looks for and finds a corresponding partition for 'today' in f1. > *Actual:* > 1. The first scheduled instance for p1 proceeds to COMPLETED, and produces a partition in f1 for 'today' > 2. However, the first scheduled instance for p2 is left in WAITING state, since it is looking for a partition in f1 for 'yesterday', which does not exist (and will never exist). > I am currently working around this unexpected behaviour by specifying the input feed range start and end for p2 as 'today(24,0)' instead of 'today(0,0)' > Please advise if this is indeed a) a bug or b) a mistake in the configuration. > Many thanks, -- This message was sent by Atlassian JIRA (v6.3.4#6332)