Re: [VOTE] Accept Druid into the Apache Incubator
+1 On 2018/02/22 19:03:55, Julian Hyde wrote: > Hi all,> > > After some discussion on the Druid proposal[1], I'd like to> > start a vote on accepting Druid into the Apache Incubator,> > per the ASF policy[2] and voting rules[3].> > > A vote for accepting a new Apache Incubator podling is a> > majority vote for which only Incubator PMC member votes are> > binding. Votes from other people are also welcome as an> > indication of people's enthusiasm (or lack thereof).> > > Please do not use this VOTE thread for discussions. If> > needed, start a new thread instead.> > > This vote will run for at least 72 hours. Please VOTE as> > follows:> > [ ] +1 Accept Druid into the Apache Incubator> > [ ] +0 Abstain> > [ ] -1 Do not accept Druid into the Apache Incubator> > because ...> > > The proposal is listed below, but you can also access it on> > the wiki[4].> > > Julian> > > [1] > https://lists.apache.org/thread.html/b95f90a30b6e8587e9b108f368b07c1b3e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E> > > > [2] > https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor> > > > [3] http://www.apache.org/foundation/voting.html> > > [4] https://wiki.apache.org/incubator/DruidProposal> > > > > > > = Druid Proposal => > > == Abstract ==> > > Druid is a high-performance, column-oriented, distributed> > data store.> > > == Proposal ==> > > Druid is an open source data store designed for real-time> > exploratory analytics on large data sets. Druid's key> > features are a column-oriented storage layout, a distributed> > shared-nothing architecture, and ability to generate and> > leverage indexing and caching structures. Druid is typically> > deployed in clusters of tens to hundreds of nodes, and has> > the ability to load data from Apache Kafka and Apache> > Hadoop, among other data sources. Druid offers two query> > languages: a SQL dialect (powered by Apache Calcite) and a> > JSON-over-HTTP API.> > > Druid was originally developed to power a slice-and-dice> > analytical UI built on top of large event streams. The> > original use case for Druid targeted ingest rates of> > millions of records/sec, retention of over a year of data,> > and query latencies of sub-second to a few seconds. Many> > people can benefit from such capability, and many already> > have (see http://druid.io/druid-powered.html). In addition,> > new use cases have emerged since Druid's original> > development, such as OLAP acceleration of data warehouse> > tables and more highly concurrent applications operating> > with relatively narrower queries.> > > == Background ==> > > Druid is a data store designed for fast analytics. It would> > typically be used in lieu of more general purpose query> > systems like Hadoop MapReduce or Spark when query latency is> > of the utmost importance. Druid is often used as a data> > store for powering GUI analytical applications.> > > The buzzwordy description of Druid is a high-performance,> > column-oriented, distributed data store. What we mean by> > this is:> > > * "high performance": Druid aims to provide low query> > latency and high ingest rates possible.> > * "column-oriented": Druid stores data in a column-oriented> > format, like most other systems designed for analytics. It> > can also store indexes along with the columns.> > * "distributed": Druid is deployed in clusters, typically of> > tens to hundreds of nodes.> > * "data store": Druid loads your data and stores a copy of> > it on the cluster's local disks (and may cache it in> > memory). It doesn't query your data from some other> > storage system.> > > == Rationale ==> > > Druid is a mature, active project with a large number of> > production installations, dozens of contributors to each> > release, and multiple vendors offering professional> > support. Given Druid's strong community, its close> > integration with many other Apache projects (such as Kafka,> > Hadoop, and Calcite), and its pre-existing Apache-inspired> > governance structure, we feel that Apache is the best home> > for the project on a long-term basis.> > > == Current Status ==> > > === Meritocracy ===> > > Since Druid was first open sourced the original developers> > have solicited contributions from others, including through> > our blog, the project mailing lists, and through accepting> > GitHub pull requests. We have an Apache-inspired governance> > structure with a PMC and committers, and our committer ranks> > include a good number of people from outside the original> > development team.> > > === Community ===> > > The Druid core developers have sought to nurture a community> > throughout the life of the project. We use GitHub as the> > focal point for bug reports and code contributions, and the> > mailing lists for most other discussion. To try to make> > people feel welcome, we've also spelled this out on a> > "CONTRIBUTE" l
Re: [VOTE] Accept Druid into the Apache Incubator
+1 (non-binding) - Xin Wang 2018-02-23 4:34 GMT+08:00 Jyotirmoy Sundi : > +1 > > On 2018/02/22 19:03:55, Julian Hyde wrote: > > Hi all,> > > > > After some discussion on the Druid proposal[1], I'd like to> > > start a vote on accepting Druid into the Apache Incubator,> > > per the ASF policy[2] and voting rules[3].> > > > > A vote for accepting a new Apache Incubator podling is a> > > majority vote for which only Incubator PMC member votes are> > > binding. Votes from other people are also welcome as an> > > indication of people's enthusiasm (or lack thereof).> > > > > Please do not use this VOTE thread for discussions. If> > > needed, start a new thread instead.> > > > > This vote will run for at least 72 hours. Please VOTE as> > > follows:> > > [ ] +1 Accept Druid into the Apache Incubator> > > [ ] +0 Abstain> > > [ ] -1 Do not accept Druid into the Apache Incubator> > > because ...> > > > > The proposal is listed below, but you can also access it on> > > the wiki[4].> > > > > Julian> > > > > [1] https://lists.apache.org/thread.html/b95f90a30b6e8587e9b108f368b07c > 1b3e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E> > > > > [2] https://incubator.apache.org/policy/incubation.html# > approval_of_proposal_by_sponsor> > > > > [3] http://www.apache.org/foundation/voting.html> > > > > [4] https://wiki.apache.org/incubator/DruidProposal> > > > > > > > > > > > > = Druid Proposal => > > > > == Abstract ==> > > > > Druid is a high-performance, column-oriented, distributed> > > data store.> > > > > == Proposal ==> > > > > Druid is an open source data store designed for real-time> > > exploratory analytics on large data sets. Druid's key> > > features are a column-oriented storage layout, a distributed> > > shared-nothing architecture, and ability to generate and> > > leverage indexing and caching structures. Druid is typically> > > deployed in clusters of tens to hundreds of nodes, and has> > > the ability to load data from Apache Kafka and Apache> > > Hadoop, among other data sources. Druid offers two query> > > languages: a SQL dialect (powered by Apache Calcite) and a> > > JSON-over-HTTP API.> > > > > Druid was originally developed to power a slice-and-dice> > > analytical UI built on top of large event streams. The> > > original use case for Druid targeted ingest rates of> > > millions of records/sec, retention of over a year of data,> > > and query latencies of sub-second to a few seconds. Many> > > people can benefit from such capability, and many already> > > have (see http://druid.io/druid-powered.html). In addition,> > > new use cases have emerged since Druid's original> > > development, such as OLAP acceleration of data warehouse> > > tables and more highly concurrent applications operating> > > with relatively narrower queries.> > > > > == Background ==> > > > > Druid is a data store designed for fast analytics. It would> > > typically be used in lieu of more general purpose query> > > systems like Hadoop MapReduce or Spark when query latency is> > > of the utmost importance. Druid is often used as a data> > > store for powering GUI analytical applications.> > > > > The buzzwordy description of Druid is a high-performance,> > > column-oriented, distributed data store. What we mean by> > > this is:> > > > > * "high performance": Druid aims to provide low query> > > latency and high ingest rates possible.> > > * "column-oriented": Druid stores data in a column-oriented> > > format, like most other systems designed for analytics. It> > > can also store indexes along with the columns.> > > * "distributed": Druid is deployed in clusters, typically of> > > tens to hundreds of nodes.> > > * "data store": Druid loads your data and stores a copy of> > > it on the cluster's local disks (and may cache it in> > > memory). It doesn't query your data from some other> > > storage system.> > > > > == Rationale ==> > > > > Druid is a mature, active project with a large number of> > > production installations, dozens of contributors to each> > > release, and multiple vendors offering professional> > > support. Given Druid's strong community, its close> > > integration with many other Apache projects (such as Kafka,> > > Hadoop, and Calcite), and its pre-existing Apache-inspired> > > governance structure, we feel that Apache is the best home> > > for the project on a long-term basis.> > > > > == Current Status ==> > > > > === Meritocracy ===> > > > > Since Druid was first open sourced the original developers> > > have solicited contributions from others, including through> > > our blog, the project mailing lists, and through accepting> > > GitHub pull requests. We have an Apache-inspired governance> > > structure with a PMC and committers, and our committer ranks> > > include a good number of people from outside the original> > > development team.> > > > > === Community ===> > > > > The Druid core developers have sought to nurture a community> > > throughout the life of the project. We use GitHub as the> > >
Re: [VOTE] Accept Druid into the Apache Incubator
+1 Vote On 2018/02/22 19:03:55, Julian Hyde wrote: > Hi all,> > > After some discussion on the Druid proposal[1], I'd like to> > start a vote on accepting Druid into the Apache Incubator,> > per the ASF policy[2] and voting rules[3].> > > A vote for accepting a new Apache Incubator podling is a> > majority vote for which only Incubator PMC member votes are> > binding. Votes from other people are also welcome as an> > indication of people's enthusiasm (or lack thereof).> > > Please do not use this VOTE thread for discussions. If> > needed, start a new thread instead.> > > This vote will run for at least 72 hours. Please VOTE as> > follows:> > [ ] +1 Accept Druid into the Apache Incubator> > [ ] +0 Abstain> > [ ] -1 Do not accept Druid into the Apache Incubator> > because ...> > > The proposal is listed below, but you can also access it on> > the wiki[4].> > > Julian> > > [1] > https://lists.apache.org/thread.html/b95f90a30b6e8587e9b108f368b07c1b3e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E> > > > [2] > https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor> > > > [3] http://www.apache.org/foundation/voting.html> > > [4] https://wiki.apache.org/incubator/DruidProposal> > > > > > > = Druid Proposal => > > == Abstract ==> > > Druid is a high-performance, column-oriented, distributed> > data store.> > > == Proposal ==> > > Druid is an open source data store designed for real-time> > exploratory analytics on large data sets. Druid's key> > features are a column-oriented storage layout, a distributed> > shared-nothing architecture, and ability to generate and> > leverage indexing and caching structures. Druid is typically> > deployed in clusters of tens to hundreds of nodes, and has> > the ability to load data from Apache Kafka and Apache> > Hadoop, among other data sources. Druid offers two query> > languages: a SQL dialect (powered by Apache Calcite) and a> > JSON-over-HTTP API.> > > Druid was originally developed to power a slice-and-dice> > analytical UI built on top of large event streams. The> > original use case for Druid targeted ingest rates of> > millions of records/sec, retention of over a year of data,> > and query latencies of sub-second to a few seconds. Many> > people can benefit from such capability, and many already> > have (see http://druid.io/druid-powered.html). In addition,> > new use cases have emerged since Druid's original> > development, such as OLAP acceleration of data warehouse> > tables and more highly concurrent applications operating> > with relatively narrower queries.> > > == Background ==> > > Druid is a data store designed for fast analytics. It would> > typically be used in lieu of more general purpose query> > systems like Hadoop MapReduce or Spark when query latency is> > of the utmost importance. Druid is often used as a data> > store for powering GUI analytical applications.> > > The buzzwordy description of Druid is a high-performance,> > column-oriented, distributed data store. What we mean by> > this is:> > > * "high performance": Druid aims to provide low query> > latency and high ingest rates possible.> > * "column-oriented": Druid stores data in a column-oriented> > format, like most other systems designed for analytics. It> > can also store indexes along with the columns.> > * "distributed": Druid is deployed in clusters, typically of> > tens to hundreds of nodes.> > * "data store": Druid loads your data and stores a copy of> > it on the cluster's local disks (and may cache it in> > memory). It doesn't query your data from some other> > storage system.> > > == Rationale ==> > > Druid is a mature, active project with a large number of> > production installations, dozens of contributors to each> > release, and multiple vendors offering professional> > support. Given Druid's strong community, its close> > integration with many other Apache projects (such as Kafka,> > Hadoop, and Calcite), and its pre-existing Apache-inspired> > governance structure, we feel that Apache is the best home> > for the project on a long-term basis.> > > == Current Status ==> > > === Meritocracy ===> > > Since Druid was first open sourced the original developers> > have solicited contributions from others, including through> > our blog, the project mailing lists, and through accepting> > GitHub pull requests. We have an Apache-inspired governance> > structure with a PMC and committers, and our committer ranks> > include a good number of people from outside the original> > development team.> > > === Community ===> > > The Druid core developers have sought to nurture a community> > throughout the life of the project. We use GitHub as the> > focal point for bug reports and code contributions, and the> > mailing lists for most other discussion. To try to make> > people feel welcome, we've also spelled
RE: [VOTE] Accept Druid into the Apache Incubator
+1 (non-binding) -Original Message- From: Jyotirmoy Sundi [mailto:sundi...@gmail.com] Sent: 23 February 2018 02:17 To: general@incubator.apache.org Subject: Re: [VOTE] Accept Druid into the Apache Incubator +1 Vote On 2018/02/22 19:03:55, Julian Hyde wrote: > Hi all,> > > After some discussion on the Druid proposal[1], I'd like to> start a > vote on accepting Druid into the Apache Incubator,> per the ASF > policy[2] and voting rules[3].> > > A vote for accepting a new Apache Incubator podling is a> majority > vote for which only Incubator PMC member votes are> binding. Votes > from other people are also welcome as an> indication of people's > enthusiasm (or lack thereof).> > > Please do not use this VOTE thread for discussions. If> needed, start > a new thread instead.> > > This vote will run for at least 72 hours. Please VOTE as> follows:> [ > ] +1 Accept Druid into the Apache Incubator> [ ] +0 Abstain> [ ] -1 > Do not accept Druid into the Apache Incubator> > because ...> > > The proposal is listed below, but you can also access it on> the > wiki[4].> > > Julian> > > [1] > https://lists.apache.org/thread.html/b95f90a30b6e8587e9b108f368b07c1b3 > e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E> > > [2] > https://incubator.apache.org/policy/incubation.html#approval_of_propos > al_by_sponsor> > > [3] http://www.apache.org/foundation/voting.html> > > [4] https://wiki.apache.org/incubator/DruidProposal> > > > > > > = Druid Proposal => > > == Abstract ==> > > Druid is a high-performance, column-oriented, distributed> data > store.> > > == Proposal ==> > > Druid is an open source data store designed for real-time> exploratory > analytics on large data sets. Druid's key> features are a > column-oriented storage layout, a distributed> shared-nothing > architecture, and ability to generate and> leverage indexing and > caching structures. Druid is typically> deployed in clusters of tens > to hundreds of nodes, and has> the ability to load data from Apache > Kafka and Apache> Hadoop, among other data sources. Druid offers two > query> > languages: a SQL dialect (powered by Apache Calcite) and a> > JSON-over-HTTP API.> > > Druid was originally developed to power a slice-and-dice> analytical > UI built on top of large event streams. The> original use case for > Druid targeted ingest rates of> millions of records/sec, retention of > over a year of data,> and query latencies of sub-second to a few > seconds. Many> people can benefit from such capability, and many > already> have (see http://druid.io/druid-powered.html). In addition,> > new use cases have emerged since Druid's original> development, such > as OLAP acceleration of data warehouse> tables and more highly > concurrent applications operating> with relatively narrower queries.> > > == Background ==> > > Druid is a data store designed for fast analytics. It would> typically > be used in lieu of more general purpose query> systems like Hadoop > MapReduce or Spark when query latency is> of the utmost importance. > Druid is often used as a data> store for powering GUI analytical > applications.> > > The buzzwordy description of Druid is a high-performance,> > column-oriented, distributed data store. What we mean by> this is:> > > * "high performance": Druid aims to provide low query> > latency and high ingest rates possible.> > * "column-oriented": Druid stores data in a column-oriented> > format, like most other systems designed for analytics. It> > can also store indexes along with the columns.> > * "distributed": Druid is deployed in clusters, typically of> > tens to hundreds of nodes.> > * "data store": Druid loads your data and stores a copy of> > it on the cluster's local disks (and may cache it in> > memory). It doesn't query your data from some other> > storage system.> > > == Rationale ==> > > Druid is a mature, active project with a large number of> production > installations, dozens of contributors to each> release, and multiple > vendors offering professional> support. Given Druid's strong > community, its close> integration with many other Apache projects > (such as Kafka,> Hadoop, and Calcite), and its pre-existing > Apache-inspired> governance structure, we feel that Apache is the best > home> for the project on a long-term basis.> > > == Current Status ==> > > === Meritocracy ===> > > Since Druid was first open sourced the original developers> have > solicited contributions from others, including through> our blog, the > project mailing lists, and through accepting> GitHub pull requests. We > have an Apache-inspired governance> structure with a PMC and > committers, and our committer ranks> include a good number of people > from outside the original> development team.> > > === Community ===> > > The Druid core developers have sought to nurture a community> > throughout the life of the project. We use GitHub as the> f
