falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pallavi Rao <pallavi....@inmobi.com>
Subject Re: Falcon bi-weekly collaboration meeting - 18th Nov 2015 - MOM
Date Mon, 23 Nov 2015 11:38:47 GMT
I can volunteer to drive the 0.9 release of Falcon, unless anyone else is
keen on taking it up.


On Wed, Nov 18, 2015 at 11:27 AM, Sandeep Samudrala <sandysmdl@gmail.com>

> Thanks all for joining the sync up. MOM as follows:
> 1. Next release in falcon would be 0.9.(Tentative timeline is around mid of
> Jan).
> 2. Timeline for code freeze, feature listing/freezing would be called out
> soon for 0.9 release.
> 3. Tentative features to come in 0.9 are Instance search, cluster update,
> ingestion as part of life cycle and native scheduler.
> 4. Ying is working on instance search and could go in 0.9.
> 5. Meetup has been pushed to Jan.
> 5. Discussions on 1.0 release.
>    - Separate branch would be cut out down the line and would work in
>    parallel with 0.9.
>    - All Features/Jiras which are backward incompatible would be tagged
>    accordingly.
>    - Spark action could be one of the candidate to go in falcon 1.0 once
>    spark action on oozie is full stabilized and working.
>    - Open up Entity(Entity revamp) to support any execution engines(Be it
>    batch/streaming or any dag engine) to run on Falcon.
>    - Falcon Binaries could be targeted as part of 1.0.
> Thanks,
> -sandeep.

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 

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message