Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6997F189F6 for ; Sat, 30 Jan 2016 07:25:14 +0000 (UTC) Received: (qmail 71094 invoked by uid 500); 30 Jan 2016 07:25:14 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 71047 invoked by uid 500); 30 Jan 2016 07:25:14 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 71036 invoked by uid 99); 30 Jan 2016 07:25:13 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Jan 2016 07:25:13 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4CBC4180619 for ; Sat, 30 Jan 2016 07:25:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=6.31 tests=[SPF_HELO_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id rLe2uo_Er1YE for ; Sat, 30 Jan 2016 07:25:04 +0000 (UTC) Received: from h19.dbweb.ee (h19.dbweb.ee [90.190.106.29]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 4F45042BCC for ; Sat, 30 Jan 2016 07:25:04 +0000 (UTC) Received: from 184-177-196-88.dyn.estpak.ee ([88.196.177.184] helo=iRack.lan) by h19.dbweb.ee with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.83) (envelope-from ) id 1aPPu2-0002Xw-7S for dev@falcon.apache.org; Sat, 30 Jan 2016 09:25:02 +0200 Subject: Re: feed retention limit To: dev@falcon.apache.org References: <56AB2DC9.3040704@roo.ee> From: Margus Roo Message-ID: <56AC6550.3070809@roo.ee> Date: Sat, 30 Jan 2016 09:25:04 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Good hint, I did not know it. Margus (margusja) Roo http://margus.roo.ee skype: margusja +372 51 48 780 On 29/01/16 11:25, Pavan Kolamuri wrote: > Hi Margus, If you just submit feed Retention won't even kick, for that you > have to schedule the feed. If you don't want to delete feed you can simply > submit the feed don't schedule . > > On Fri, Jan 29, 2016 at 2:45 PM, Margus Roo wrote: > >> Hi >> >> First of all - great tool! >> >> Unless there is no user list, I try here to share my thoughts. >> We are trying to use falcon live production one project related telecom. >> >> What I noticed and maybe I do something wrong but marking feed retention >> limit like: >> >> >> I can successfully submit feed using falcon entity -type feed -submit >> -file [feed-file-name] >> >> But digging into yarn logs I found that my feed is deleted unless I put >> retention limit and action. >> >> After it I used Falcon GUI and discovered that retention limit is allowed >> max two digits. So max is 99? >> >> So what I can conclude from that. Fallback is delete? >> >> -- >> Margus (margusja) Roo >> http://margus.roo.ee >> skype: margusja >> +372 51 48 780 >> >> >