falcon-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ajayyad...@apache.org
Subject falcon git commit: FALCON-1574 Document behavior of lifecycle retention stage frequency behavior. Contributed by Sowmya Ramesh.
Date Mon, 02 Nov 2015 12:25:07 GMT
Repository: falcon
Updated Branches:
  refs/heads/master ffd2b7862 -> 15771e863

FALCON-1574 Document behavior of lifecycle retention stage frequency behavior. Contributed
by Sowmya Ramesh.

Project: http://git-wip-us.apache.org/repos/asf/falcon/repo
Commit: http://git-wip-us.apache.org/repos/asf/falcon/commit/15771e86
Tree: http://git-wip-us.apache.org/repos/asf/falcon/tree/15771e86
Diff: http://git-wip-us.apache.org/repos/asf/falcon/diff/15771e86

Branch: refs/heads/master
Commit: 15771e863d69d1ee3128194d8e0d52ab98f842ad
Parents: ffd2b78
Author: Ajay Yadava <ajaynsit@gmail.com>
Authored: Mon Nov 2 17:21:38 2015 +0530
Committer: Ajay Yadava <ajaynsit@gmail.com>
Committed: Mon Nov 2 17:22:55 2015 +0530

 CHANGES.txt                                   | 2 ++
 docs/src/site/twiki/EntitySpecification.twiki | 4 ++++
 2 files changed, 6 insertions(+)

diff --git a/CHANGES.txt b/CHANGES.txt
index 28cbd2b..b7b4dc9 100755
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -49,6 +49,8 @@ Branch : 0.8 (Proposed Release version: 0.8)
     FALCON-1027 Falcon proxy user support(Sowmya Ramesh)
+    FALCON-1574 Document behavior of lifecycle retention stage frequency behavior(Sowmya
Ramesh via Ajay Yadava).
     FALCON-1564 Provide an option for users to disable system post-processing JMS notification
(Pallavi Rao) 
     FALCON-1519 Suspend And Resume API's in Falcon Unit(Narayan Periwal via Pallavi Rao)

diff --git a/docs/src/site/twiki/EntitySpecification.twiki b/docs/src/site/twiki/EntitySpecification.twiki
index b357c44..c4f5f76 100644
--- a/docs/src/site/twiki/EntitySpecification.twiki
+++ b/docs/src/site/twiki/EntitySpecification.twiki
@@ -435,6 +435,10 @@ the existing one which is to delete all instances corresponding to instance-time
 Property "retention.policy.agebaseddelete.limit" is a mandatory property and must contain
a valid duration e.g. "hours(1)"
+Retention frequency is not a mandatory parameter. If user doesn't specify the frequency in
the retention stage then
+it doesn't fallback to old retention policy frequency. Its default value is set to 6 hours
if feed frequency is less
+than 6 hours else its set to feed frequency as retention shouldn't be more frequent than
data availability to avoid
+wastage of compute resources.
 In future, we will allow more customisation like customising how to choose instances to be
deleted through this method.

View raw message