Re: [VOTE] Accept Falcon into the Apache Incubator (was originally named Ivory)
+1 (binding) On Thu, Mar 21, 2013 at 7:32 PM, Niall Pemberton wrote: > +1 to Falcon - or whatever name it finalises on! > > Niall > > On Thu, Mar 21, 2013 at 4:54 AM, Srikanth Sundarrajan > wrote: > > Hi, > > > > Thanks for participating in the proposal discussion on Falcon > > (formerly Ivory). I'd like to call a VOTE for acceptance of Apache > > Falcon into the Incubator. I'll let the vote run till (Tue 3/26 6pm IST). > > > > [ ] +1 Accept Apache Falcon into the Incubator > > [ ] +0 Don't care. > > [ ] -1 Don't accept Apache Falcon into the Incubator because... > > > > Full proposal is pasted at the bottom of this email, and the > > corresponding wiki is http://wiki.apache.org/incubator/FalconProposal. > > > > > > Only VOTEs from Incubator PMC members are binding, but all are welcome > > to express their thoughts. > > > > Thanks, > > Srikanth Sundarrajan > > = Falcon Proposal = > > > > == Abstract == > > Falcon is a data processing and management solution for Hadoop > > designed for data motion, coordination of data pipelines, lifecycle > > management, and data discovery. Falcon enables end consumers to > > quickly onboard their data and its associated processing and > > management tasks on Hadoop clusters. > > > > == Proposal == > > Falcon will enable easy data management via declarative mechanism for > > Hadoop. Users of Falcon platform simply define infrastructure > > endpoints, data sets and processing rules declaratively. These > > declarative configurations are expressed in such a way that the > > dependencies between these configured entities are explicitly > > described. This information about inter-dependencies between various > > entities allows Falcon to orchestrate and manage various data > > management functions. > > > > The key use cases that Falcon addresses are: > > * Data Motion > > * Process orchestration and scheduling > > * Policy-based Lifecycle Management > > * Data Discovery > > * Operability/Usability > > > > With these features it is possible for users to onboard their data > > sets with a comprehensive and holistic understanding of how, when and > > where their data is managed across its lifecycle. Complex functions > > such as retrying failures, identifying possible SLA breaches or > > automated handling of input data changes are now simple directives. > > All the administrative functions and user level functions are > > available via RESTful APIs. CLI is simply a wrapper over the RESTful > > APIs. > > > > == Background == > > Hadoop and its ecosystem of products have made storing and processing > > massive amounts of data commonplace. This has enabled numerous > > organizations to gain valuable insights that they never could have > > achieved in the past. While it is easy to leverage Hadoop for > > crunching large volumes of data, organizing data, managing life cycle > > of data and processing data is fairly involved. This is solved > > adequately well in a classic data platform involving data warehouses > > and standard ETL (extract-transform-load) tools, but remains largely > > unsolved today. In addition to data processing complexities, Hadoop > > presents new sets of challenges and opportunities relating to > > management of data. > > > > Data Management on Hadoop encompasses data motion, process > > orchestration, lifecycle management, data discovery, etc. among other > > concerns that are beyond ETL. Falcon is a new data processing and > > management platform for Hadoop that solves this problem and creates > > additional opportunities by building on existing components within the > > Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without > > reinventing the wheel. Falcon has been in production at InMobi, going > > on its second year and has been managing hundreds of feeds and > > processes. > > > > Falcon is being developed by engineers employed with InMobi and > > Hortonworks. This platform addition will increase the adoption of > > Apache Hadoop by driving data management tractable for end users. We > > are therefore proposing to make Falcon an Apache open source project. > > > > == Rationale == > > The Falcon project aims to improve the usability of Apache Hadoop. As > > a result Apache Hadoop will grow its community of users by increasing > > the places Hadoop can be utilized and the use cases it will solve. By > > developing Falcon in Apache we hope to gather a diverse community of > > contributors, helping to ensure that Falcon is deployable for a broad > > range of scenarios. Members of the Hadoop development community will > > be able to influence Falcon’s roadmap, and contribute to it. We > > believe having Falcon as part of the Apache Hadoop ecosystem will be a > > great benefit to all of Hadoop's users. > > > > == Current Status == > > Falcon is widely deployed in production within InMobi and moving on to > > its second year. A version with a valuable set of features is > > developed by the list of initial committers and is hosted o
Re: [VOTE] Accept Falcon into the Apache Incubator (was originally named Ivory)
+1 to Falcon - or whatever name it finalises on! Niall On Thu, Mar 21, 2013 at 4:54 AM, Srikanth Sundarrajan wrote: > Hi, > > Thanks for participating in the proposal discussion on Falcon > (formerly Ivory). I'd like to call a VOTE for acceptance of Apache > Falcon into the Incubator. I'll let the vote run till (Tue 3/26 6pm IST). > > [ ] +1 Accept Apache Falcon into the Incubator > [ ] +0 Don't care. > [ ] -1 Don't accept Apache Falcon into the Incubator because... > > Full proposal is pasted at the bottom of this email, and the > corresponding wiki is http://wiki.apache.org/incubator/FalconProposal. > > > Only VOTEs from Incubator PMC members are binding, but all are welcome > to express their thoughts. > > Thanks, > Srikanth Sundarrajan > = Falcon Proposal = > > == Abstract == > Falcon is a data processing and management solution for Hadoop > designed for data motion, coordination of data pipelines, lifecycle > management, and data discovery. Falcon enables end consumers to > quickly onboard their data and its associated processing and > management tasks on Hadoop clusters. > > == Proposal == > Falcon will enable easy data management via declarative mechanism for > Hadoop. Users of Falcon platform simply define infrastructure > endpoints, data sets and processing rules declaratively. These > declarative configurations are expressed in such a way that the > dependencies between these configured entities are explicitly > described. This information about inter-dependencies between various > entities allows Falcon to orchestrate and manage various data > management functions. > > The key use cases that Falcon addresses are: > * Data Motion > * Process orchestration and scheduling > * Policy-based Lifecycle Management > * Data Discovery > * Operability/Usability > > With these features it is possible for users to onboard their data > sets with a comprehensive and holistic understanding of how, when and > where their data is managed across its lifecycle. Complex functions > such as retrying failures, identifying possible SLA breaches or > automated handling of input data changes are now simple directives. > All the administrative functions and user level functions are > available via RESTful APIs. CLI is simply a wrapper over the RESTful > APIs. > > == Background == > Hadoop and its ecosystem of products have made storing and processing > massive amounts of data commonplace. This has enabled numerous > organizations to gain valuable insights that they never could have > achieved in the past. While it is easy to leverage Hadoop for > crunching large volumes of data, organizing data, managing life cycle > of data and processing data is fairly involved. This is solved > adequately well in a classic data platform involving data warehouses > and standard ETL (extract-transform-load) tools, but remains largely > unsolved today. In addition to data processing complexities, Hadoop > presents new sets of challenges and opportunities relating to > management of data. > > Data Management on Hadoop encompasses data motion, process > orchestration, lifecycle management, data discovery, etc. among other > concerns that are beyond ETL. Falcon is a new data processing and > management platform for Hadoop that solves this problem and creates > additional opportunities by building on existing components within the > Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without > reinventing the wheel. Falcon has been in production at InMobi, going > on its second year and has been managing hundreds of feeds and > processes. > > Falcon is being developed by engineers employed with InMobi and > Hortonworks. This platform addition will increase the adoption of > Apache Hadoop by driving data management tractable for end users. We > are therefore proposing to make Falcon an Apache open source project. > > == Rationale == > The Falcon project aims to improve the usability of Apache Hadoop. As > a result Apache Hadoop will grow its community of users by increasing > the places Hadoop can be utilized and the use cases it will solve. By > developing Falcon in Apache we hope to gather a diverse community of > contributors, helping to ensure that Falcon is deployable for a broad > range of scenarios. Members of the Hadoop development community will > be able to influence Falcon’s roadmap, and contribute to it. We > believe having Falcon as part of the Apache Hadoop ecosystem will be a > great benefit to all of Hadoop's users. > > == Current Status == > Falcon is widely deployed in production within InMobi and moving on to > its second year. A version with a valuable set of features is > developed by the list of initial committers and is hosted on github. > > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Falcon following the Apache meritocracy > model. We have wanted to make the project open source and encourage > contributors from multiple o
[FYI] Fwd: [VOTE] Community Vote: Graduate Apache Onami to become an ASF TLD
Fellow IPMC-members, because of the confusion my last community vote to graduate the Onami podling has caused we restarted the vote. Now here comes the notification that the community is currently voting on its graduation from the incubator on our dev list. If you have any concerns and/or would like to express your opinion, you are welcome to drop your message on our dev list. Regards, Christian -- Forwarded message -- From: Christian Grobmeier Date: Thu, Mar 21, 2013 at 7:30 PM Subject: [VOTE] Community Vote: Graduate Apache Onami to become an ASF TLD To: d...@onami.incubator.apache.org Hi all, this is the vote for the ONAMI COMMUNITY to demonstrate our willingness demonstrate our willingness to become a self govern top level project of the Apache Software Foundation. The community is everybody with commit rights (considered binding) and of course everybody else who has an interest in this podling (considered non-binding). So far we have not had an objections against graduation. Please vote +1 if you feel Apache Onami is ready to become a top level project. [ ] +1, we are ready to become a top level project [ ] -1, please stay in the incubator, because... The vote is open for 72h. With this vote the previous vote on the same matter is not longer valid and can be considered closed. Best regards, Christian -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Falcon into the Apache Incubator (was originally named Ivory)
+1. Alan. On Mar 20, 2013, at 9:54 PM, Srikanth Sundarrajan wrote: > Hi, > > Thanks for participating in the proposal discussion on Falcon > (formerly Ivory). I'd like to call a VOTE for acceptance of Apache > Falcon into the Incubator. I'll let the vote run till (Tue 3/26 6pm IST). > > [ ] +1 Accept Apache Falcon into the Incubator > [ ] +0 Don't care. > [ ] -1 Don't accept Apache Falcon into the Incubator because... > > Full proposal is pasted at the bottom of this email, and the > corresponding wiki is http://wiki.apache.org/incubator/FalconProposal. > > > Only VOTEs from Incubator PMC members are binding, but all are welcome > to express their thoughts. > > Thanks, > Srikanth Sundarrajan > = Falcon Proposal = > > == Abstract == > Falcon is a data processing and management solution for Hadoop > designed for data motion, coordination of data pipelines, lifecycle > management, and data discovery. Falcon enables end consumers to > quickly onboard their data and its associated processing and > management tasks on Hadoop clusters. > > == Proposal == > Falcon will enable easy data management via declarative mechanism for > Hadoop. Users of Falcon platform simply define infrastructure > endpoints, data sets and processing rules declaratively. These > declarative configurations are expressed in such a way that the > dependencies between these configured entities are explicitly > described. This information about inter-dependencies between various > entities allows Falcon to orchestrate and manage various data > management functions. > > The key use cases that Falcon addresses are: > * Data Motion > * Process orchestration and scheduling > * Policy-based Lifecycle Management > * Data Discovery > * Operability/Usability > > With these features it is possible for users to onboard their data > sets with a comprehensive and holistic understanding of how, when and > where their data is managed across its lifecycle. Complex functions > such as retrying failures, identifying possible SLA breaches or > automated handling of input data changes are now simple directives. > All the administrative functions and user level functions are > available via RESTful APIs. CLI is simply a wrapper over the RESTful > APIs. > > == Background == > Hadoop and its ecosystem of products have made storing and processing > massive amounts of data commonplace. This has enabled numerous > organizations to gain valuable insights that they never could have > achieved in the past. While it is easy to leverage Hadoop for > crunching large volumes of data, organizing data, managing life cycle > of data and processing data is fairly involved. This is solved > adequately well in a classic data platform involving data warehouses > and standard ETL (extract-transform-load) tools, but remains largely > unsolved today. In addition to data processing complexities, Hadoop > presents new sets of challenges and opportunities relating to > management of data. > > Data Management on Hadoop encompasses data motion, process > orchestration, lifecycle management, data discovery, etc. among other > concerns that are beyond ETL. Falcon is a new data processing and > management platform for Hadoop that solves this problem and creates > additional opportunities by building on existing components within the > Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without > reinventing the wheel. Falcon has been in production at InMobi, going > on its second year and has been managing hundreds of feeds and > processes. > > Falcon is being developed by engineers employed with InMobi and > Hortonworks. This platform addition will increase the adoption of > Apache Hadoop by driving data management tractable for end users. We > are therefore proposing to make Falcon an Apache open source project. > > == Rationale == > The Falcon project aims to improve the usability of Apache Hadoop. As > a result Apache Hadoop will grow its community of users by increasing > the places Hadoop can be utilized and the use cases it will solve. By > developing Falcon in Apache we hope to gather a diverse community of > contributors, helping to ensure that Falcon is deployable for a broad > range of scenarios. Members of the Hadoop development community will > be able to influence Falcon’s roadmap, and contribute to it. We > believe having Falcon as part of the Apache Hadoop ecosystem will be a > great benefit to all of Hadoop's users. > > == Current Status == > Falcon is widely deployed in production within InMobi and moving on to > its second year. A version with a valuable set of features is > developed by the list of initial committers and is hosted on github. > > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Falcon following the Apache meritocracy > model. We have wanted to make the project open source and encourage > contributors from multiple organizations from the start. We plan t
Re: [VOTE] Accept Falcon into the Apache Incubator (was originally named Ivory)
+1 (binding) -C On Wed, Mar 20, 2013 at 9:54 PM, Srikanth Sundarrajan wrote: > Hi, > > Thanks for participating in the proposal discussion on Falcon > (formerly Ivory). I'd like to call a VOTE for acceptance of Apache > Falcon into the Incubator. I'll let the vote run till (Tue 3/26 6pm IST). > > [ ] +1 Accept Apache Falcon into the Incubator > [ ] +0 Don't care. > [ ] -1 Don't accept Apache Falcon into the Incubator because... > > Full proposal is pasted at the bottom of this email, and the > corresponding wiki is http://wiki.apache.org/incubator/FalconProposal. > > > Only VOTEs from Incubator PMC members are binding, but all are welcome > to express their thoughts. > > Thanks, > Srikanth Sundarrajan > = Falcon Proposal = > > == Abstract == > Falcon is a data processing and management solution for Hadoop > designed for data motion, coordination of data pipelines, lifecycle > management, and data discovery. Falcon enables end consumers to > quickly onboard their data and its associated processing and > management tasks on Hadoop clusters. > > == Proposal == > Falcon will enable easy data management via declarative mechanism for > Hadoop. Users of Falcon platform simply define infrastructure > endpoints, data sets and processing rules declaratively. These > declarative configurations are expressed in such a way that the > dependencies between these configured entities are explicitly > described. This information about inter-dependencies between various > entities allows Falcon to orchestrate and manage various data > management functions. > > The key use cases that Falcon addresses are: > * Data Motion > * Process orchestration and scheduling > * Policy-based Lifecycle Management > * Data Discovery > * Operability/Usability > > With these features it is possible for users to onboard their data > sets with a comprehensive and holistic understanding of how, when and > where their data is managed across its lifecycle. Complex functions > such as retrying failures, identifying possible SLA breaches or > automated handling of input data changes are now simple directives. > All the administrative functions and user level functions are > available via RESTful APIs. CLI is simply a wrapper over the RESTful > APIs. > > == Background == > Hadoop and its ecosystem of products have made storing and processing > massive amounts of data commonplace. This has enabled numerous > organizations to gain valuable insights that they never could have > achieved in the past. While it is easy to leverage Hadoop for > crunching large volumes of data, organizing data, managing life cycle > of data and processing data is fairly involved. This is solved > adequately well in a classic data platform involving data warehouses > and standard ETL (extract-transform-load) tools, but remains largely > unsolved today. In addition to data processing complexities, Hadoop > presents new sets of challenges and opportunities relating to > management of data. > > Data Management on Hadoop encompasses data motion, process > orchestration, lifecycle management, data discovery, etc. among other > concerns that are beyond ETL. Falcon is a new data processing and > management platform for Hadoop that solves this problem and creates > additional opportunities by building on existing components within the > Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without > reinventing the wheel. Falcon has been in production at InMobi, going > on its second year and has been managing hundreds of feeds and > processes. > > Falcon is being developed by engineers employed with InMobi and > Hortonworks. This platform addition will increase the adoption of > Apache Hadoop by driving data management tractable for end users. We > are therefore proposing to make Falcon an Apache open source project. > > == Rationale == > The Falcon project aims to improve the usability of Apache Hadoop. As > a result Apache Hadoop will grow its community of users by increasing > the places Hadoop can be utilized and the use cases it will solve. By > developing Falcon in Apache we hope to gather a diverse community of > contributors, helping to ensure that Falcon is deployable for a broad > range of scenarios. Members of the Hadoop development community will > be able to influence Falcon’s roadmap, and contribute to it. We > believe having Falcon as part of the Apache Hadoop ecosystem will be a > great benefit to all of Hadoop's users. > > == Current Status == > Falcon is widely deployed in production within InMobi and moving on to > its second year. A version with a valuable set of features is > developed by the list of initial committers and is hosted on github. > > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Falcon following the Apache meritocracy > model. We have wanted to make the project open source and encourage > contributors from multiple organizations from the start. We plan to
Re: [VOTE] Accept Falcon into the Apache Incubator (was originally named Ivory)
On Thu, Mar 21, 2013 at 12:07 PM, Srikanth Sundarrajan wrote: > ...Since the VOTE is already out, I will leave it so. > However, we will continue to watch out for any serious objections/concern > with the name "Falcon" Ok, fine with me - just make sure there's enough time for people to comment on that before closing the vote. Thanks! -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Falcon into the Apache Incubator (was originally named Ivory)
Thanks Bertrand. Since the VOTE is already out, I will leave it so. However, we will continue to watch out for any serious objections/concern with the name "Falcon". Regards Srikanth Sundarrajan On Thu, Mar 21, 2013 at 2:46 PM, Bertrand Delacretaz wrote: > On Thu, Mar 21, 2013 at 5:54 AM, Srikanth Sundarrajan > wrote: > > ...Thanks for participating in the proposal discussion on Falcon > > (formerly Ivory). I'd like to call a VOTE for acceptance of Apache > > Falcon into the Incubator... > > I hate to slow down things, but considering that the name change to > Falcon was only announced 4 hours ago, and there are some concerns > about it in the discussion thread, I'd say the discussion hasn't > sufficiently settled down to vote. > > We usually allow at least 24 hours for lazy consensus, doing that for > this name change would be good IMO, especially as the discussion > thread shows that Falcon is far from being a unique name. > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- _ 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: [VOTE] Accept Falcon into the Apache Incubator (was originally named Ivory)
+1 (non-binding) On Thu, Mar 21, 2013 at 10:24 AM, Srikanth Sundarrajan < srikanth.sundarra...@inmobi.com> wrote: > Hi, > > Thanks for participating in the proposal discussion on Falcon > (formerly Ivory). I'd like to call a VOTE for acceptance of Apache > Falcon into the Incubator. I'll let the vote run till (Tue 3/26 6pm IST). > > [ ] +1 Accept Apache Falcon into the Incubator > [ ] +0 Don't care. > [ ] -1 Don't accept Apache Falcon into the Incubator because... > > Full proposal is pasted at the bottom of this email, and the > corresponding wiki is http://wiki.apache.org/incubator/FalconProposal. > > > Only VOTEs from Incubator PMC members are binding, but all are welcome > to express their thoughts. > > Thanks, > Srikanth Sundarrajan > = Falcon Proposal = > > == Abstract == > Falcon is a data processing and management solution for Hadoop > designed for data motion, coordination of data pipelines, lifecycle > management, and data discovery. Falcon enables end consumers to > quickly onboard their data and its associated processing and > management tasks on Hadoop clusters. > > == Proposal == > Falcon will enable easy data management via declarative mechanism for > Hadoop. Users of Falcon platform simply define infrastructure > endpoints, data sets and processing rules declaratively. These > declarative configurations are expressed in such a way that the > dependencies between these configured entities are explicitly > described. This information about inter-dependencies between various > entities allows Falcon to orchestrate and manage various data > management functions. > > The key use cases that Falcon addresses are: > * Data Motion > * Process orchestration and scheduling > * Policy-based Lifecycle Management > * Data Discovery > * Operability/Usability > > With these features it is possible for users to onboard their data > sets with a comprehensive and holistic understanding of how, when and > where their data is managed across its lifecycle. Complex functions > such as retrying failures, identifying possible SLA breaches or > automated handling of input data changes are now simple directives. > All the administrative functions and user level functions are > available via RESTful APIs. CLI is simply a wrapper over the RESTful > APIs. > > == Background == > Hadoop and its ecosystem of products have made storing and processing > massive amounts of data commonplace. This has enabled numerous > organizations to gain valuable insights that they never could have > achieved in the past. While it is easy to leverage Hadoop for > crunching large volumes of data, organizing data, managing life cycle > of data and processing data is fairly involved. This is solved > adequately well in a classic data platform involving data warehouses > and standard ETL (extract-transform-load) tools, but remains largely > unsolved today. In addition to data processing complexities, Hadoop > presents new sets of challenges and opportunities relating to > management of data. > > Data Management on Hadoop encompasses data motion, process > orchestration, lifecycle management, data discovery, etc. among other > concerns that are beyond ETL. Falcon is a new data processing and > management platform for Hadoop that solves this problem and creates > additional opportunities by building on existing components within the > Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without > reinventing the wheel. Falcon has been in production at InMobi, going > on its second year and has been managing hundreds of feeds and > processes. > > Falcon is being developed by engineers employed with InMobi and > Hortonworks. This platform addition will increase the adoption of > Apache Hadoop by driving data management tractable for end users. We > are therefore proposing to make Falcon an Apache open source project. > > == Rationale == > The Falcon project aims to improve the usability of Apache Hadoop. As > a result Apache Hadoop will grow its community of users by increasing > the places Hadoop can be utilized and the use cases it will solve. By > developing Falcon in Apache we hope to gather a diverse community of > contributors, helping to ensure that Falcon is deployable for a broad > range of scenarios. Members of the Hadoop development community will > be able to influence Falcon’s roadmap, and contribute to it. We > believe having Falcon as part of the Apache Hadoop ecosystem will be a > great benefit to all of Hadoop's users. > > == Current Status == > Falcon is widely deployed in production within InMobi and moving on to > its second year. A version with a valuable set of features is > developed by the list of initial committers and is hosted on github. > > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Falcon following the Apache meritocracy > model. We have wanted to make the project open source and encourage > contributors from multiple orga
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
Hi, > I agree with that - if the Flex PMC thinks otherwise they should speak up now. I don't see any issues (different software space) but will ask the rest of the Flex PMC. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Falcon into the Apache Incubator (was originally named Ivory)
On Thu, Mar 21, 2013 at 5:54 AM, Srikanth Sundarrajan wrote: > ...Thanks for participating in the proposal discussion on Falcon > (formerly Ivory). I'd like to call a VOTE for acceptance of Apache > Falcon into the Incubator... I hate to slow down things, but considering that the name change to Falcon was only announced 4 hours ago, and there are some concerns about it in the discussion thread, I'd say the discussion hasn't sufficiently settled down to vote. We usually allow at least 24 hours for lazy consensus, doing that for this name change would be good IMO, especially as the discussion thread shows that Falcon is far from being a unique name. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
On Thu, Mar 21, 2013 at 6:02 AM, Srikanth Sundarrajan wrote: >...I am assuming it won't be an issue as Falcon used within the > Adobe/Apache Flex isn't related to Hadoop... I agree with that - if the Flex PMC thinks otherwise they should speak up now. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
Please find that the MRQL mailing lists have been created and are ready to be used for further discussion: d...@mrql.incubator.apache.org u...@mrql.incubator.apache.org priv...@mrql.incubator.apache.org Would everyone named on the proposal please go subscribe to them, and happy MRQL'ing. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
Also the name of the dominant credit card fraud detection system. Everybody loves the name. On Thu, Mar 21, 2013 at 6:16 AM, David Jencks wrote: > Falcon is also the name of a database engine: > > http://en.wikipedia.org/wiki/Falcon_(storage_engine) > > the name of a programming language > > http://falconpl.org/project_docs/core/index.html > > and very close to the name of some kind of oracle add on vendor: > > > http://www.falconstor.com/solutions/business-applications/oracle-database-solutions > > david jencks > > On Mar 20, 2013, at 10:02 PM, Srikanth Sundarrajan < > srikanth.sundarra...@inmobi.com> wrote: > > > Hi Justin, > >I am assuming it won't be an issue as Falcon used within the > > Adobe/Apache Flex isn't related to Hadoop. > > > > Regards > > Srikanth Sundarrajan > > > > On Thu, Mar 21, 2013 at 10:23 AM, Justin Mclean >wrote: > > > >> Hi, > >> > >> JFYI Falcon is already a name used by Adobe and Apache Flex. It's an AS > >> compiler and an experimental AS to JS compiler (Falcon JS) - not sure if > >> that is an issue or not. > >> > >> Justin > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > >> > > > > -- > > _ > > 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. > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Accept Falcon into the Apache Incubator (was originally named Ivory)
+1 (binding) Arun On Mar 21, 2013, at 5:55 AM, Srikanth Sundarrajan wrote: > Hi, > > Thanks for participating in the proposal discussion on Falcon > (formerly Ivory). I'd like to call a VOTE for acceptance of Apache > Falcon into the Incubator. I'll let the vote run till (Tue 3/26 6pm IST). > > [ ] +1 Accept Apache Falcon into the Incubator > [ ] +0 Don't care. > [ ] -1 Don't accept Apache Falcon into the Incubator because... > > Full proposal is pasted at the bottom of this email, and the > corresponding wiki is http://wiki.apache.org/incubator/FalconProposal. > > > Only VOTEs from Incubator PMC members are binding, but all are welcome > to express their thoughts. > > Thanks, > Srikanth Sundarrajan > = Falcon Proposal = > > == Abstract == > Falcon is a data processing and management solution for Hadoop > designed for data motion, coordination of data pipelines, lifecycle > management, and data discovery. Falcon enables end consumers to > quickly onboard their data and its associated processing and > management tasks on Hadoop clusters. > > == Proposal == > Falcon will enable easy data management via declarative mechanism for > Hadoop. Users of Falcon platform simply define infrastructure > endpoints, data sets and processing rules declaratively. These > declarative configurations are expressed in such a way that the > dependencies between these configured entities are explicitly > described. This information about inter-dependencies between various > entities allows Falcon to orchestrate and manage various data > management functions. > > The key use cases that Falcon addresses are: > * Data Motion > * Process orchestration and scheduling > * Policy-based Lifecycle Management > * Data Discovery > * Operability/Usability > > With these features it is possible for users to onboard their data > sets with a comprehensive and holistic understanding of how, when and > where their data is managed across its lifecycle. Complex functions > such as retrying failures, identifying possible SLA breaches or > automated handling of input data changes are now simple directives. > All the administrative functions and user level functions are > available via RESTful APIs. CLI is simply a wrapper over the RESTful > APIs. > > == Background == > Hadoop and its ecosystem of products have made storing and processing > massive amounts of data commonplace. This has enabled numerous > organizations to gain valuable insights that they never could have > achieved in the past. While it is easy to leverage Hadoop for > crunching large volumes of data, organizing data, managing life cycle > of data and processing data is fairly involved. This is solved > adequately well in a classic data platform involving data warehouses > and standard ETL (extract-transform-load) tools, but remains largely > unsolved today. In addition to data processing complexities, Hadoop > presents new sets of challenges and opportunities relating to > management of data. > > Data Management on Hadoop encompasses data motion, process > orchestration, lifecycle management, data discovery, etc. among other > concerns that are beyond ETL. Falcon is a new data processing and > management platform for Hadoop that solves this problem and creates > additional opportunities by building on existing components within the > Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without > reinventing the wheel. Falcon has been in production at InMobi, going > on its second year and has been managing hundreds of feeds and > processes. > > Falcon is being developed by engineers employed with InMobi and > Hortonworks. This platform addition will increase the adoption of > Apache Hadoop by driving data management tractable for end users. We > are therefore proposing to make Falcon an Apache open source project. > > == Rationale == > The Falcon project aims to improve the usability of Apache Hadoop. As > a result Apache Hadoop will grow its community of users by increasing > the places Hadoop can be utilized and the use cases it will solve. By > developing Falcon in Apache we hope to gather a diverse community of > contributors, helping to ensure that Falcon is deployable for a broad > range of scenarios. Members of the Hadoop development community will > be able to influence Falcon’s roadmap, and contribute to it. We > believe having Falcon as part of the Apache Hadoop ecosystem will be a > great benefit to all of Hadoop's users. > > == Current Status == > Falcon is widely deployed in production within InMobi and moving on to > its second year. A version with a valuable set of features is > developed by the list of initial committers and is hosted on github. > > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Falcon following the Apache meritocracy > model. We have wanted to make the project open source and encourage > contributors from multiple organizations from the start. We plan to > pro
Re: all podlings please update and maintain project metadata
Daniel Shahaf wrote on Thu, Mar 21, 2013 at 09:34:24 +0200: > David Crossley wrote on Thu, Mar 21, 2013 at 17:52:26 +1100: > > Christian Grobmeier wrote: > > > Daniel Shahaf wrote: > > > > Shane Curcuru wrote: > > > >> > > > >> Separately, I'd love to hear any comments about how this kind of > > > >> requirement is expressed in the graduation guides. I.e. is it clear, > > > >> even to normal humans (i.e. 99.99% of the world who are not Incubator > > > >> experts) that these things are required of TLPs before (and after) > > > >> graduation? > > > > > > > > FWIW, https://www.apache.org/dev/infra-contact#requesting-graduation > > > > seems to be read and followed by most graduating projects. > > > > Ah, maybe we have identified the breakdown. Perhaps they skip > > the Incubator documentation. > > > > I reckon that we need to link in both directions. > > > > Agreed: linking from #requesting-podling to the incubator.a.o page > documenting the overall process from the podling's POV would make sense. > Go for it :) The point applies to both #requesting-podling and #requesting-graduation. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: all podlings please update and maintain project metadata
David Crossley wrote on Thu, Mar 21, 2013 at 17:52:26 +1100: > Christian Grobmeier wrote: > > Daniel Shahaf wrote: > > > Shane Curcuru wrote: > > >> > > >> Separately, I'd love to hear any comments about how this kind of > > >> requirement is expressed in the graduation guides. I.e. is it clear, > > >> even to normal humans (i.e. 99.99% of the world who are not Incubator > > >> experts) that these things are required of TLPs before (and after) > > >> graduation? > > > > > > FWIW, https://www.apache.org/dev/infra-contact#requesting-graduation > > > seems to be read and followed by most graduating projects. > > Ah, maybe we have identified the breakdown. Perhaps they skip > the Incubator documentation. > > I reckon that we need to link in both directions. > Agreed: linking from #requesting-podling to the incubator.a.o page documenting the overall process from the podling's POV would make sense. Go for it :) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
