Praveen,
+1.

How about adding feed retention based on number of instances (using
lifecycle framework) to the list?

Thanks,
Pallavi

On Sun, Dec 25, 2016 at 10:57 AM, Venkat Ranganathan <
[email protected]> wrote:

> +1
>
> Thanks for taking up the release
>
> Venkat
> ________________________________________
> From: Jean-Baptiste Onofré <[email protected]>
> Sent: Saturday, December 24, 2016 1:29 AM
> To: [email protected]
> Subject: Re: Apache Falcon 0.11 release - Scope
>
> Hi,
>
> it sounds good to me.
>
> Thanks,
> Regards
> JB
>
> On 12/24/2016 10:05 AM, praveen adlakha wrote:
> > Hi All,
> >
> > Apache Falcon team aims to make frequent releases. In keeping up with
> this
> > commitment, I think the following features are ready to be rolled out for
> > the 0.11 release.
> >
> >
> >    - Support of Non-Trusted extensions in Distributed Mode/Embedded Mode
> [
> >    FALCON-2182 <https://issues.apache.org/jira/browse/FALCON-2182>].
> >    - Backlog Metrics in graphite[FALCON-2170
> >    <https://issues.apache.org/jira/browse/FALCON-2170>].
> >    - Falcon Shell support for entity and instance commands[FALCON-1596
> >    <https://issues.apache.org/jira/browse/FALCON-1596>].
> >    - Support to disable PostProcessing and moving logs from Server[
> >    FALCON-2039 <https://issues.apache.org/jira/browse/FALCON-2039>].
> >
> >
> > Please let me know if there are any more features and enhancements that
> you
> > wish to include in the release.Once the scope is freeze will come up with
> > timelines.
> >
>
> --
> Jean-Baptiste Onofré
> [email protected]
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>

-- 
_____________________________________________________________
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.

Reply via email to