Re: [PROPOSAL] Propose Howl as an Apache Incubator project
The proposal looks fine, but the name collides with http://howl.ow2.org/ -Brian On Thu, Feb 10, 2011 at 1:37 PM, Alan Gates wrote: > I would like to propose Howl as an Apache Incubator project. Howl is a > table and storage management service for data created using Apache Hadoop. > The proposal is on the Incubator wiki at > http://wiki.apache.org/incubator/HowlProposal and is pasted below. Thanks. > > Alan. > > == Abstract == > Howl is a table and storage management service for data created using Apache > Hadoop. > > == Proposal == > The vision of Howl is to provide table management and storage management > layers for Apache Hadoop. This includes: > * Providing a shared schema and data type mechanism. > * Providing a table abstraction so that users need not be concerned with > where or how their data is stored. > * Providing interoperability across data processing tools such as Pig, Map > Reduce, Streaming, and Hive. > > == Background == > Data processors using Apache Hadoop have a common need for table management > services. The goal of a table management service is to track data that > exists in a Hadoop grid and present that data to users in a tabular format. > Such a table management service needs to provide a single input and output > format to users so that individual users need not be concerned with the > storage formats that are chosen for particular data sets. As part of having > a single format, the data will need to be described by one type of schema > and have a single datatype system. > > Additionally, users should be free to choose the best tools for their use > cases. The Hadoop project includes Map Reduce, Streaming, Pig, and Hive, > and additional tools exist such as Cascading. Each of these tools has users > who prefer it, and there are use cases best addressed by each of these > tools. Two users on the same grid who need to share data should not be > constrained to use the same tool but rather should be free to choose the > best tool for their use case. A table management service that presents data > in the same way to all of the tools can alleviate this problem by providing > interfaces to each of the data processing tools. > > There are also a few other features a table management service should > provide, such as notification of when data arrives. > > A couple of developers at Yahoo! started the project. It is based on the > Hive !MetaStore component. There is good amount of interest in such a > service expressed from Yahoo!, Facebook, !LinkedIn, and, others. We are > therefore proposing to place Howl in the Apache incubator and to build an > open source community around it. > > > == Rationale == > There is a strong need for a table management service, especially for large > grids with petabytes of data, and where the data volume is increasing by the > day. Hadoop users need to find data to read and have a place to store their > data. Currently users must understand the location of data to read, the > storage format, compression techniques used, etc. To write data they need > to understand where on HDFS their data belongs, the best compression format > to use, how their data should be serialized, etc. > > Most users do not want to be concerned with these issues. They want these > managed for them. > > Having it as an Apache Open Source project will highly benefit Howl from the > point of view of getting a large community that currently uses Hadoop and > the other products built around Hadoop (like Pig, Hive, etc.). Users of the > Hadoop ecosystem can influence Howl’s roadmap, and contribute to it. Looking > at it in another way, we believe having Howl as part of the Hadoop ecosystem > will be a great benefit to the current Hadoop/Pig/Hive community too. > > == Current Status == > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Howl 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 provide plenty of support > to new developers and to quickly recruit those who make solid contributions > to committer status. > > === Community === > Howl is currently being used by developers at Yahoo! and there has been an > expressed interest from !LinkedIn and Facebook. Yahoo! also plans to deploy > the current version of Howl in production soon. We hope to extend the user > and developer base further in the future. The current developers and users > are all interested in building a solid open source community around Howl. > > To work towards an open source community, we have started using the !GitHub > issue tracker and mailing lists at Yahoo! for development discussions within > our group. > > === Core Developers === > Howl is currently being developed by four engineers from Yahoo! - Devaraj > Das, Ashutosh Chauhan, Sushanth Sowmyan, and Mac Yang. All the engineers > have deep expertise i
Re: [PROPOSAL] Propose Howl as an Apache Incubator project
Good catch, but allow me to disagree with you. Howl here is a name, while OW2 HOWL is an acronym for "High-speed ObjectWeb Logger" and on [1] it is all written in capital letters. [1] - http://howl.ow2.org/ On Sun, Feb 13, 2011 at 5:52 PM, Brian McCallister wrote: > The proposal looks fine, but the name collides with http://howl.ow2.org/ > > -Brian > > On Thu, Feb 10, 2011 at 1:37 PM, Alan Gates wrote: >> I would like to propose Howl as an Apache Incubator project. Howl is a >> table and storage management service for data created using Apache Hadoop. >> The proposal is on the Incubator wiki at >> http://wiki.apache.org/incubator/HowlProposal and is pasted below. Thanks. >> >> Alan. >> >> == Abstract == >> Howl is a table and storage management service for data created using Apache >> Hadoop. >> >> == Proposal == >> The vision of Howl is to provide table management and storage management >> layers for Apache Hadoop. This includes: >> * Providing a shared schema and data type mechanism. >> * Providing a table abstraction so that users need not be concerned with >> where or how their data is stored. >> * Providing interoperability across data processing tools such as Pig, Map >> Reduce, Streaming, and Hive. >> >> == Background == >> Data processors using Apache Hadoop have a common need for table management >> services. The goal of a table management service is to track data that >> exists in a Hadoop grid and present that data to users in a tabular format. >> Such a table management service needs to provide a single input and output >> format to users so that individual users need not be concerned with the >> storage formats that are chosen for particular data sets. As part of having >> a single format, the data will need to be described by one type of schema >> and have a single datatype system. >> >> Additionally, users should be free to choose the best tools for their use >> cases. The Hadoop project includes Map Reduce, Streaming, Pig, and Hive, >> and additional tools exist such as Cascading. Each of these tools has users >> who prefer it, and there are use cases best addressed by each of these >> tools. Two users on the same grid who need to share data should not be >> constrained to use the same tool but rather should be free to choose the >> best tool for their use case. A table management service that presents data >> in the same way to all of the tools can alleviate this problem by providing >> interfaces to each of the data processing tools. >> >> There are also a few other features a table management service should >> provide, such as notification of when data arrives. >> >> A couple of developers at Yahoo! started the project. It is based on the >> Hive !MetaStore component. There is good amount of interest in such a >> service expressed from Yahoo!, Facebook, !LinkedIn, and, others. We are >> therefore proposing to place Howl in the Apache incubator and to build an >> open source community around it. >> >> >> == Rationale == >> There is a strong need for a table management service, especially for large >> grids with petabytes of data, and where the data volume is increasing by the >> day. Hadoop users need to find data to read and have a place to store their >> data. Currently users must understand the location of data to read, the >> storage format, compression techniques used, etc. To write data they need >> to understand where on HDFS their data belongs, the best compression format >> to use, how their data should be serialized, etc. >> >> Most users do not want to be concerned with these issues. They want these >> managed for them. >> >> Having it as an Apache Open Source project will highly benefit Howl from the >> point of view of getting a large community that currently uses Hadoop and >> the other products built around Hadoop (like Pig, Hive, etc.). Users of the >> Hadoop ecosystem can influence Howl’s roadmap, and contribute to it. Looking >> at it in another way, we believe having Howl as part of the Hadoop ecosystem >> will be a great benefit to the current Hadoop/Pig/Hive community too. >> >> == Current Status == >> === Meritocracy === >> Our intent with this incubator proposal is to start building a diverse >> developer community around Howl 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 provide plenty of support >> to new developers and to quickly recruit those who make solid contributions >> to committer status. >> >> === Community === >> Howl is currently being used by developers at Yahoo! and there has been an >> expressed interest from !LinkedIn and Facebook. Yahoo! also plans to deploy >> the current version of Howl in production soon. We hope to extend the user >> and developer base further in the future. The current developers and users >> are all interested in building a solid open source community around Howl. >> >> To work
Re: [PROPOSAL] Propose Howl as an Apache Incubator project
There as well exists a Zeroconf implementation called Howl and I am pretty certain that some other projects are using that name too. Cheers Daniel On Sun, Feb 13, 2011 at 6:57 PM, Mohammad Nour El-Din wrote: > Good catch, but allow me to disagree with you. Howl here is a name, > while OW2 HOWL is an acronym for "High-speed ObjectWeb Logger" and on > [1] it is all written in capital letters. > > [1] - http://howl.ow2.org/ > > On Sun, Feb 13, 2011 at 5:52 PM, Brian McCallister wrote: >> The proposal looks fine, but the name collides with http://howl.ow2.org/ >> >> -Brian >> >> On Thu, Feb 10, 2011 at 1:37 PM, Alan Gates wrote: >>> I would like to propose Howl as an Apache Incubator project. Howl is a >>> table and storage management service for data created using Apache Hadoop. >>> The proposal is on the Incubator wiki at >>> http://wiki.apache.org/incubator/HowlProposal and is pasted below. Thanks. >>> >>> Alan. >>> >>> == Abstract == >>> Howl is a table and storage management service for data created using Apache >>> Hadoop. >>> >>> == Proposal == >>> The vision of Howl is to provide table management and storage management >>> layers for Apache Hadoop. This includes: >>> * Providing a shared schema and data type mechanism. >>> * Providing a table abstraction so that users need not be concerned with >>> where or how their data is stored. >>> * Providing interoperability across data processing tools such as Pig, Map >>> Reduce, Streaming, and Hive. >>> >>> == Background == >>> Data processors using Apache Hadoop have a common need for table management >>> services. The goal of a table management service is to track data that >>> exists in a Hadoop grid and present that data to users in a tabular format. >>> Such a table management service needs to provide a single input and output >>> format to users so that individual users need not be concerned with the >>> storage formats that are chosen for particular data sets. As part of having >>> a single format, the data will need to be described by one type of schema >>> and have a single datatype system. >>> >>> Additionally, users should be free to choose the best tools for their use >>> cases. The Hadoop project includes Map Reduce, Streaming, Pig, and Hive, >>> and additional tools exist such as Cascading. Each of these tools has users >>> who prefer it, and there are use cases best addressed by each of these >>> tools. Two users on the same grid who need to share data should not be >>> constrained to use the same tool but rather should be free to choose the >>> best tool for their use case. A table management service that presents data >>> in the same way to all of the tools can alleviate this problem by providing >>> interfaces to each of the data processing tools. >>> >>> There are also a few other features a table management service should >>> provide, such as notification of when data arrives. >>> >>> A couple of developers at Yahoo! started the project. It is based on the >>> Hive !MetaStore component. There is good amount of interest in such a >>> service expressed from Yahoo!, Facebook, !LinkedIn, and, others. We are >>> therefore proposing to place Howl in the Apache incubator and to build an >>> open source community around it. >>> >>> >>> == Rationale == >>> There is a strong need for a table management service, especially for large >>> grids with petabytes of data, and where the data volume is increasing by the >>> day. Hadoop users need to find data to read and have a place to store their >>> data. Currently users must understand the location of data to read, the >>> storage format, compression techniques used, etc. To write data they need >>> to understand where on HDFS their data belongs, the best compression format >>> to use, how their data should be serialized, etc. >>> >>> Most users do not want to be concerned with these issues. They want these >>> managed for them. >>> >>> Having it as an Apache Open Source project will highly benefit Howl from the >>> point of view of getting a large community that currently uses Hadoop and >>> the other products built around Hadoop (like Pig, Hive, etc.). Users of the >>> Hadoop ecosystem can influence Howl’s roadmap, and contribute to it. Looking >>> at it in another way, we believe having Howl as part of the Hadoop ecosystem >>> will be a great benefit to the current Hadoop/Pig/Hive community too. >>> >>> == Current Status == >>> === Meritocracy === >>> Our intent with this incubator proposal is to start building a diverse >>> developer community around Howl 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 provide plenty of support >>> to new developers and to quickly recruit those who make solid contributions >>> to committer status. >>> >>> === Community === >>> Howl is currently being used by developers at Yahoo! and there has been an >>> expressed inte
Missing reports: Bluesky, Deltacloud, HISE, Mesos, Stonehenge
Hi... Dear Mentors, all of these reports are still missing from [1]. Would you please make sure that it is provided and signed max by tomorrow Monday 13 February 2011. Looking forward your feedbacks. [1] - http://wiki.apache.org/incubator/February2011 -- Thanks - Mohammad Nour Author of (WebSphere Application Server Community Edition 2.0 User Guide) http://www.redbooks.ibm.com/abstracts/sg247585.html - LinkedIn: http://www.linkedin.com/in/mnour - Blog: http://tadabborat.blogspot.com "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein "Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best." - Clean Code: A Handbook of Agile Software Craftsmanship "Stay hungry, stay foolish." - Steve Jobs - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
