[
https://issues.apache.org/jira/browse/FALCON-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14108997#comment-14108997
]
Shwetha G S commented on FALCON-630:
------------------------------------
{quote}
Also, in replication, we will have a cluster pair but will only have one
cluster for all other lifecycles. How do we make this seamless instead of
having to add this at 100 places?
{quote}
This is for passing lifecycle params to the functions like schedule/instance
APIs?
> late data rerun for process broken in trunk
> --------------------------------------------
>
> Key: FALCON-630
> URL: https://issues.apache.org/jira/browse/FALCON-630
> Project: Falcon
> Issue Type: Bug
> Components: rerun
> Affects Versions: 0.5
> Reporter: Samarth Gupta
> Assignee: Shwetha G S
> Priority: Blocker
> Attachments: FALCON-630-v2.patch, FALCON-630.patch
>
>
> late data rerun for process is not working . it seems like in pre processing
> record size is storing data by Feed name and not by input name , due to which
> late data is never detected.
> {code}
> -falconInputFeeds
> FETL2-RRLog#FETL-RTBS-PRLog#FETL-RTBS-NPRLog
> {code}
> above even though param in tasktracker logs says InputFeeds , they are
> actually feed name.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
