You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by Margus Roo <ma...@roo.ee> on 2016/01/29 10:15:53 UTC
feed retention limit
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:
<retention limit="months(9999999)" action="archive" />
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
Re: feed retention limit
Posted by Margus Roo <ma...@roo.ee>.
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 <ma...@roo.ee> 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:
>> <retention limit="months(9999999)" action="archive" />
>>
>> 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
>>
>>
>
Re: feed retention limit
Posted by Pavan Kolamuri <pa...@inmobi.com>.
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 <ma...@roo.ee> 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:
> <retention limit="months(9999999)" action="archive" />
>
> 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
>
>
--
Thanks and regards
Pavan Kumar Kolamuri
--
_____________________________________________________________
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally privileged
information. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking any action in reliance
on the contents of this information is strictly prohibited and may be
unlawful. If you have received this communication in error, please notify
us immediately by responding to this email and then delete it from your
system. The firm is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.
Re: feed retention limit
Posted by Ajay Yadav <aj...@gmail.com>.
Thank you, reporting issues is an important form of contribution and we
appreciate it :) Let us know if you face any issues.
On Fri, Jan 29, 2016 at 3:13 PM, Margus Roo <ma...@roo.ee> wrote:
> Thanks for replay and I try to create jira task. It is my first try so it
> may take some time :)
>
> Margus (margusja) Roo
> http://margus.roo.ee
> skype: margusja
> +372 51 48 780
>
> On 29/01/16 11:39, Ajay Yadava wrote:
>
>> thrown an error if you had chosen action as archive and
>> submitted the feed from command line, so that is a bug in my view. Ideally
>> UI validation should be same as backend validation, so that is also a bug
>> in my opinion. It will be very helpful if you can file a JIRA with these
>> details (and relevant cluster + feed entity definition).
>>
>
>
Re: feed retention limit
Posted by Margus Roo <ma...@roo.ee>.
Thanks for replay and I try to create jira task. It is my first try so
it may take some time :)
Margus (margusja) Roo
http://margus.roo.ee
skype: margusja
+372 51 48 780
On 29/01/16 11:39, Ajay Yadava wrote:
> thrown an error if you had chosen action as archive and
> submitted the feed from command line, so that is a bug in my view. Ideally
> UI validation should be same as backend validation, so that is also a bug
> in my opinion. It will be very helpful if you can file a JIRA with these
> details (and relevant cluster + feed entity definition).
Re: feed retention limit
Posted by Ajay Yadava <aj...@apache.org>.
Currently retention supports only delete action and there is no max limit
for retention on falcon server as far as I can recall. There was a plan to
support other actions but we have moved to the new lifecycle framework to
solve for those use cases and we will soon provide those capabilities also.
It should have thrown an error if you had chosen action as archive and
submitted the feed from command line, so that is a bug in my view. Ideally
UI validation should be same as backend validation, so that is also a bug
in my opinion. It will be very helpful if you can file a JIRA with these
details (and relevant cluster + feed entity definition).
By the way there is a user mailing list: user@falcon.apache.org (ccd here
for benefit of all users also) and most of developers are also subscribed
to the user mailing list.
On Fri, Jan 29, 2016 at 2:45 PM, Margus Roo <ma...@roo.ee> 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:
> <retention limit="months(9999999)" action="archive" />
>
> 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
>
>
Re: feed retention limit
Posted by Ajay Yadava <aj...@apache.org>.
Currently retention supports only delete action and there is no max limit
for retention on falcon server as far as I can recall. There was a plan to
support other actions but we have moved to the new lifecycle framework to
solve for those use cases and we will soon provide those capabilities also.
It should have thrown an error if you had chosen action as archive and
submitted the feed from command line, so that is a bug in my view. Ideally
UI validation should be same as backend validation, so that is also a bug
in my opinion. It will be very helpful if you can file a JIRA with these
details (and relevant cluster + feed entity definition).
By the way there is a user mailing list: user@falcon.apache.org (ccd here
for benefit of all users also) and most of developers are also subscribed
to the user mailing list.
On Fri, Jan 29, 2016 at 2:45 PM, Margus Roo <ma...@roo.ee> 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:
> <retention limit="months(9999999)" action="archive" />
>
> 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
>
>