You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Pallavi Rao (JIRA)" <ji...@apache.org> on 2015/08/06 13:54:04 UTC
[jira] [Comment Edited] (FALCON-1375) Adding latePolicy element in
feed definition
[ https://issues.apache.org/jira/browse/FALCON-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659707#comment-14659707 ]
Pallavi Rao edited comment on FALCON-1375 at 8/6/15 11:54 AM:
--------------------------------------------------------------
These properties were introduced as part of FALCON-1204.
I agree these should be more of entity level properties coz., each feed has a different frequency. The runtime properties can be treated as defaults if none is specified in the entity.
was (Author: pallavi.rao):
These properties were introduced as part of FALCON-1024.
I agree these should be more of entity level properties coz., each feed has a different frequency. The runtime properties can be treated as defaults if none is specified in the entity.
> Adding latePolicy element in feed definition
> --------------------------------------------
>
> Key: FALCON-1375
> URL: https://issues.apache.org/jira/browse/FALCON-1375
> Project: Falcon
> Issue Type: Improvement
> Components: feed
> Affects Versions: trunk
> Reporter: Pragya Mittal
>
> As of now feed replication honours late policy but there is no way we can overwrite this property via feed definition.feed only exposes <late-arrival cut-off="days(100000)"/>
> The late policy is defined in runtime.properties :
> {code}
> *.feed.late.allowed=true
> *.feed.late.frequency=hours(3)
> *.feed.late.policy=exp-backoff
> {code}
> If user wants to overwrite these properties(changing late policy or frequency) , they have to be explicitly changed in runtime.properties. Setting these via feed definition would reduce such overheads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)