Re: [DISCUSS] Druid incubation proposal

[Julian Hyde]

It seems that we have consensus (and indeed, an ectopic vote is
happening in this discuss thread). I will start a formal vote. All of
you who replied '+1' on this thread, thanks for your support, and
please cast your vote on the formal thread.

Julian


On Thu, Feb 22, 2018 at 9:36 AM, Pramod Immaneni  wrote:
> +1
>
> On Fri, Feb 16, 2018 at 12:15 PM, Gian Merlino  wrote:
>
>> Hi all,
>>
>> I would like to open up a discussion about incubating Druid at Apache. I've
>> included a proposal in this mail and have also posted a draft at
>> https://wiki.apache.org/incubator/DruidProposal. More information about
>> Druid is also available on our project web site at: http://druid.io/
>>
>> Thanks for your consideration!
>>
>> Gian
>>
>> = 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"
>> link from the project page: http://druid.io/community/. Today we have an
>> active contributor base (a typical release has ~40 contributors) and
>> mailing list.
>>
>> === Core Developers ===
>>
>> Druid enjoys good diversity of committer affiliation. The most active
>> developers over the past year are affiliated with four different companies:
>> Imply, Metamarkets, Yahoo, and Hortonworks. Many Druid committers are also
>> committers on other ASF projects as well, including Apache Airflow, Apache
>> Curator, and Apache Calcite. The original developers of Druid remain
>> involved in the project.

Re: [DISCUSS] Druid incubation proposal

[Pramod Immaneni]

+1

On Fri, Feb 16, 2018 at 12:15 PM, Gian Merlino  wrote:

> Hi all,
>
> I would like to open up a discussion about incubating Druid at Apache. I've
> included a proposal in this mail and have also posted a draft at
> https://wiki.apache.org/incubator/DruidProposal. More information about
> Druid is also available on our project web site at: http://druid.io/
>
> Thanks for your consideration!
>
> Gian
>
> = 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"
> link from the project page: http://druid.io/community/. Today we have an
> active contributor base (a typical release has ~40 contributors) and
> mailing list.
>
> === Core Developers ===
>
> Druid enjoys good diversity of committer affiliation. The most active
> developers over the past year are affiliated with four different companies:
> Imply, Metamarkets, Yahoo, and Hortonworks. Many Druid committers are also
> committers on other ASF projects as well, including Apache Airflow, Apache
> Curator, and Apache Calcite. The original developers of Druid remain
> involved in the project.
>
> === Alignment ===
>
> Druid's current governance structure is Apache-inspired with a PMC and
> committers chosen by a meritocratic process. Additionally, Druid integrates
> with a number of other Apache projects, including Kafka, Hadoop, Hive,
> Calcite, Superset (incubating), Spark, Curator, and !ZooKeeper.
>
> == Known Risks ==
>
> === Orphaned products ===
>
> The risk of Druid becoming orphaned is low, due to a diverse 

Re: [DISCUSS] Druid incubation proposal

[Amol Kekre]

+1. Great to see Druid joining ASF.


Thks,
Amol



E:a...@datatorrent.com | M: 510-449-2606 | Twitter: @*amolhkekre*

www.datatorrent.com


On Thu, Feb 22, 2018 at 8:57 AM, Brian McCallister  wrote:

> +1 - glad to see Druid finally (hopefully) landing here!
>
> On Wed, Feb 21, 2018 at 10:57 PM, Henning Schmiedehausen <
> henn...@schmiedehausen.org> wrote:
>
> > Woot!
> >
> > +1 for druid incubation.
> >
> > -h
> >
> >
> >
> > On Fri, Feb 16, 2018 at 12:15 PM, Gian Merlino  wrote:
> >
> > > Hi all,
> > >
> > > I would like to open up a discussion about incubating Druid at Apache.
> > I've
> > > included a proposal in this mail and have also posted a draft at
> > > https://wiki.apache.org/incubator/DruidProposal. More information
> about
> > > Druid is also available on our project web site at: http://druid.io/
> > >
> > > Thanks for your consideration!
> > >
> > > Gian
> > >
> > > = 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"
> > > link from the project page: http://druid.io/community/. Today we have
> an
> > > active contributor base (a typical release has ~40 contributors) and
> > > mailing 

Re: [DISCUSS] Druid incubation proposal

[Brian McCallister]

+1 - glad to see Druid finally (hopefully) landing here!

On Wed, Feb 21, 2018 at 10:57 PM, Henning Schmiedehausen <
henn...@schmiedehausen.org> wrote:

> Woot!
>
> +1 for druid incubation.
>
> -h
>
>
>
> On Fri, Feb 16, 2018 at 12:15 PM, Gian Merlino  wrote:
>
> > Hi all,
> >
> > I would like to open up a discussion about incubating Druid at Apache.
> I've
> > included a proposal in this mail and have also posted a draft at
> > https://wiki.apache.org/incubator/DruidProposal. More information about
> > Druid is also available on our project web site at: http://druid.io/
> >
> > Thanks for your consideration!
> >
> > Gian
> >
> > = 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"
> > link from the project page: http://druid.io/community/. Today we have an
> > active contributor base (a typical release has ~40 contributors) and
> > mailing list.
> >
> > === Core Developers ===
> >
> > Druid enjoys good diversity of committer affiliation. The most active
> > developers over the past year are affiliated with four different
> companies:
> > Imply, Metamarkets, Yahoo, and Hortonworks. Many Druid committers are
> also
> > committers on other ASF projects as well, including Apache Airflow,
> Apache
> > Curator, and Apache Calcite. The original developers of Druid remain
> > involved in the project.
> >
> > === 

Re: [DISCUSS] Druid incubation proposal

[Henning Schmiedehausen]

Woot!

+1 for druid incubation.

-h



On Fri, Feb 16, 2018 at 12:15 PM, Gian Merlino  wrote:

> Hi all,
>
> I would like to open up a discussion about incubating Druid at Apache. I've
> included a proposal in this mail and have also posted a draft at
> https://wiki.apache.org/incubator/DruidProposal. More information about
> Druid is also available on our project web site at: http://druid.io/
>
> Thanks for your consideration!
>
> Gian
>
> = 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"
> link from the project page: http://druid.io/community/. Today we have an
> active contributor base (a typical release has ~40 contributors) and
> mailing list.
>
> === Core Developers ===
>
> Druid enjoys good diversity of committer affiliation. The most active
> developers over the past year are affiliated with four different companies:
> Imply, Metamarkets, Yahoo, and Hortonworks. Many Druid committers are also
> committers on other ASF projects as well, including Apache Airflow, Apache
> Curator, and Apache Calcite. The original developers of Druid remain
> involved in the project.
>
> === Alignment ===
>
> Druid's current governance structure is Apache-inspired with a PMC and
> committers chosen by a meritocratic process. Additionally, Druid integrates
> with a number of other Apache projects, including Kafka, Hadoop, Hive,
> Calcite, Superset (incubating), Spark, Curator, and !ZooKeeper.
>
> == Known Risks ==
>
> === Orphaned products ===
>
> The risk of Druid becoming 

Re: [DISCUSS] Druid incubation proposal

[Jordan Zimmerman]

+1 For Druid at ASF - great project for Apache

> On Feb 16, 2018, at 3:15 PM, Gian Merlino  wrote:
> 
> Hi all,
> 
> I would like to open up a discussion about incubating Druid at Apache. I've
> included a proposal in this mail and have also posted a draft at
> https://wiki.apache.org/incubator/DruidProposal. More information about
> Druid is also available on our project web site at: http://druid.io/
> 
> Thanks for your consideration!
> 
> Gian
> 
> = 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"
> link from the project page: http://druid.io/community/. Today we have an
> active contributor base (a typical release has ~40 contributors) and
> mailing list.
> 
> === Core Developers ===
> 
> Druid enjoys good diversity of committer affiliation. The most active
> developers over the past year are affiliated with four different companies:
> Imply, Metamarkets, Yahoo, and Hortonworks. Many Druid committers are also
> committers on other ASF projects as well, including Apache Airflow, Apache
> Curator, and Apache Calcite. The original developers of Druid remain
> involved in the project.
> 
> === Alignment ===
> 
> Druid's current governance structure is Apache-inspired with a PMC and
> committers chosen by a meritocratic process. Additionally, Druid integrates
> with a number of other Apache projects, including Kafka, Hadoop, Hive,
> Calcite, Superset (incubating), Spark, Curator, and !ZooKeeper.
> 
> == Known Risks ==
> 
> === Orphaned products ===
> 
> 

Re: [DISCUSS] Druid incubation proposal

[Chris Mattmann]

+1 from me...

Chris

On 2/21/18, 7:08 PM, "Selvamohan Neethiraj"  wrote:

+1 for adding Druid to ASF

Thanks,
Selva-

> On Feb 21, 2018, at 10:03 PM, Jitendra Pandey  
wrote:
> 
> +1
> Druid will be a great addition to ASF.
> 
> On 2/21/18, 5:06 PM, "Ashutosh Chauhan"  wrote:
> 
>+1 for Druid in ASF.
>I have been involved with Hive Druid integration. If you are looking 
for
>mentors, happy to help.
> 
>Thanks,
>Ashutosh
> 
>On Fri, Feb 16, 2018 at 2:20 PM, Tom Barber  wrote:
> 
>> I can second most of that from the peanut gallery, my high level
>> interactions with a few Druid folk and keeping a watchful eye on a very
>> exciting project over the last few years.
>> 
>> I think the Druid project would make an excellent addition to the ASF
>> portfolio.
>> 
>> Tom
>> 
>> 
>> On 16/02/18 22:17, Julian Hyde wrote:
>> 
>>> As Champion for this proposal, let me say that the Druid project will be
>>> an excellent addition to the ASF. I have been an observer of the project
>>> for a couple of years, and in many respects it is already operating in 
the
>>> Apache Way. Druid had paid developers from a number of companies, some 
of
>>> whom were in competition, and its governance was strong enough to 
navigate
>>> the choppy waters that that can create.
>>> 
>>> A number of Druid committers subsequently started to work on Apache
>>> projects (Gian on Calcite, and Slim and Nishant on Hive) and so already
>>> know what to expect.
>>> 
>>> You can get a sense of the project dynamic by reading the archives of
>>> their dev list: 
https://groups.google.com/forum/#!forum/druid-development
>>> 
>>> 
>>> Julian
>>> 
>>> 
>>> On Feb 16, 2018, at 12:15 PM, Gian Merlino  wrote:
 
 Hi all,
 
 I would like to open up a discussion about incubating Druid at Apache.
 I've
 included a proposal in this mail and have also posted a draft at
 https://wiki.apache.org/incubator/DruidProposal. More information about
 Druid is also available on our project web site at: http://druid.io/
 
 Thanks for your consideration!
 
 Gian
 
 = 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
 

Re: [DISCUSS] Druid incubation proposal

[Selvamohan Neethiraj]

+1 for adding Druid to ASF

Thanks,
Selva-

> On Feb 21, 2018, at 10:03 PM, Jitendra Pandey  
> wrote:
> 
> +1
> Druid will be a great addition to ASF.
> 
> On 2/21/18, 5:06 PM, "Ashutosh Chauhan"  wrote:
> 
>+1 for Druid in ASF.
>I have been involved with Hive Druid integration. If you are looking for
>mentors, happy to help.
> 
>Thanks,
>Ashutosh
> 
>On Fri, Feb 16, 2018 at 2:20 PM, Tom Barber  wrote:
> 
>> I can second most of that from the peanut gallery, my high level
>> interactions with a few Druid folk and keeping a watchful eye on a very
>> exciting project over the last few years.
>> 
>> I think the Druid project would make an excellent addition to the ASF
>> portfolio.
>> 
>> Tom
>> 
>> 
>> On 16/02/18 22:17, Julian Hyde wrote:
>> 
>>> As Champion for this proposal, let me say that the Druid project will be
>>> an excellent addition to the ASF. I have been an observer of the project
>>> for a couple of years, and in many respects it is already operating in the
>>> Apache Way. Druid had paid developers from a number of companies, some of
>>> whom were in competition, and its governance was strong enough to navigate
>>> the choppy waters that that can create.
>>> 
>>> A number of Druid committers subsequently started to work on Apache
>>> projects (Gian on Calcite, and Slim and Nishant on Hive) and so already
>>> know what to expect.
>>> 
>>> You can get a sense of the project dynamic by reading the archives of
>>> their dev list: https://groups.google.com/forum/#!forum/druid-development
>>> 
>>> 
>>> Julian
>>> 
>>> 
>>> On Feb 16, 2018, at 12:15 PM, Gian Merlino  wrote:
 
 Hi all,
 
 I would like to open up a discussion about incubating Druid at Apache.
 I've
 included a proposal in this mail and have also posted a draft at
 https://wiki.apache.org/incubator/DruidProposal. More information about
 Druid is also available on our project web site at: http://druid.io/
 
 Thanks for your consideration!
 
 Gian
 
 = 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
 

Re: [DISCUSS] Druid incubation proposal

[Jitendra Pandey]

+1  
Druid will be a great addition to ASF.

On 2/21/18, 5:06 PM, "Ashutosh Chauhan"  wrote:

+1 for Druid in ASF.
I have been involved with Hive Druid integration. If you are looking for
mentors, happy to help.

Thanks,
Ashutosh

On Fri, Feb 16, 2018 at 2:20 PM, Tom Barber  wrote:

> I can second most of that from the peanut gallery, my high level
> interactions with a few Druid folk and keeping a watchful eye on a very
> exciting project over the last few years.
>
> I think the Druid project would make an excellent addition to the ASF
> portfolio.
>
> Tom
>
>
> On 16/02/18 22:17, Julian Hyde wrote:
>
>> As Champion for this proposal, let me say that the Druid project will be
>> an excellent addition to the ASF. I have been an observer of the project
>> for a couple of years, and in many respects it is already operating in 
the
>> Apache Way. Druid had paid developers from a number of companies, some of
>> whom were in competition, and its governance was strong enough to 
navigate
>> the choppy waters that that can create.
>>
>> A number of Druid committers subsequently started to work on Apache
>> projects (Gian on Calcite, and Slim and Nishant on Hive) and so already
>> know what to expect.
>>
>> You can get a sense of the project dynamic by reading the archives of
>> their dev list: https://groups.google.com/forum/#!forum/druid-development
>> 
>>
>> Julian
>>
>>
>> On Feb 16, 2018, at 12:15 PM, Gian Merlino  wrote:
>>>
>>> Hi all,
>>>
>>> I would like to open up a discussion about incubating Druid at Apache.
>>> I've
>>> included a proposal in this mail and have also posted a draft at
>>> https://wiki.apache.org/incubator/DruidProposal. More information about
>>> Druid is also available on our project web site at: http://druid.io/
>>>
>>> Thanks for your consideration!
>>>
>>> Gian
>>>
>>> = 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 

Re: [DISCUSS] Druid incubation proposal

[Ashutosh Chauhan]

+1 for Druid in ASF.
I have been involved with Hive Druid integration. If you are looking for
mentors, happy to help.

Thanks,
Ashutosh

On Fri, Feb 16, 2018 at 2:20 PM, Tom Barber  wrote:

> I can second most of that from the peanut gallery, my high level
> interactions with a few Druid folk and keeping a watchful eye on a very
> exciting project over the last few years.
>
> I think the Druid project would make an excellent addition to the ASF
> portfolio.
>
> Tom
>
>
> On 16/02/18 22:17, Julian Hyde wrote:
>
>> As Champion for this proposal, let me say that the Druid project will be
>> an excellent addition to the ASF. I have been an observer of the project
>> for a couple of years, and in many respects it is already operating in the
>> Apache Way. Druid had paid developers from a number of companies, some of
>> whom were in competition, and its governance was strong enough to navigate
>> the choppy waters that that can create.
>>
>> A number of Druid committers subsequently started to work on Apache
>> projects (Gian on Calcite, and Slim and Nishant on Hive) and so already
>> know what to expect.
>>
>> You can get a sense of the project dynamic by reading the archives of
>> their dev list: https://groups.google.com/forum/#!forum/druid-development
>> 
>>
>> Julian
>>
>>
>> On Feb 16, 2018, at 12:15 PM, Gian Merlino  wrote:
>>>
>>> Hi all,
>>>
>>> I would like to open up a discussion about incubating Druid at Apache.
>>> I've
>>> included a proposal in this mail and have also posted a draft at
>>> https://wiki.apache.org/incubator/DruidProposal. More information about
>>> Druid is also available on our project web site at: http://druid.io/
>>>
>>> Thanks for your consideration!
>>>
>>> Gian
>>>
>>> = 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 

Re: [DISCUSS] Druid incubation proposal

[Tom Barber]

I can second most of that from the peanut gallery, my high level 
interactions with a few Druid folk and keeping a watchful eye on a very 
exciting project over the last few years.


I think the Druid project would make an excellent addition to the ASF 
portfolio.


Tom

On 16/02/18 22:17, Julian Hyde wrote:

As Champion for this proposal, let me say that the Druid project will be an 
excellent addition to the ASF. I have been an observer of the project for a 
couple of years, and in many respects it is already operating in the Apache 
Way. Druid had paid developers from a number of companies, some of whom were in 
competition, and its governance was strong enough to navigate the choppy waters 
that that can create.

A number of Druid committers subsequently started to work on Apache projects 
(Gian on Calcite, and Slim and Nishant on Hive) and so already know what to 
expect.

You can get a sense of the project dynamic by reading the archives of their dev list: 
https://groups.google.com/forum/#!forum/druid-development 


Julian



On Feb 16, 2018, at 12:15 PM, Gian Merlino  wrote:

Hi all,

I would like to open up a discussion about incubating Druid at Apache. I've
included a proposal in this mail and have also posted a draft at
https://wiki.apache.org/incubator/DruidProposal. More information about
Druid is also available on our project web site at: http://druid.io/

Thanks for your consideration!

Gian

= 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"
link from the project page: http://druid.io/community/. Today we have an
active 

Re: [DISCUSS] Druid incubation proposal

[Julian Hyde]

As Champion for this proposal, let me say that the Druid project will be an 
excellent addition to the ASF. I have been an observer of the project for a 
couple of years, and in many respects it is already operating in the Apache 
Way. Druid had paid developers from a number of companies, some of whom were in 
competition, and its governance was strong enough to navigate the choppy waters 
that that can create.

A number of Druid committers subsequently started to work on Apache projects 
(Gian on Calcite, and Slim and Nishant on Hive) and so already know what to 
expect. 

You can get a sense of the project dynamic by reading the archives of their dev 
list: https://groups.google.com/forum/#!forum/druid-development 


Julian


> On Feb 16, 2018, at 12:15 PM, Gian Merlino  wrote:
> 
> Hi all,
> 
> I would like to open up a discussion about incubating Druid at Apache. I've
> included a proposal in this mail and have also posted a draft at
> https://wiki.apache.org/incubator/DruidProposal. More information about
> Druid is also available on our project web site at: http://druid.io/
> 
> Thanks for your consideration!
> 
> Gian
> 
> = 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"
> link from the project page: http://druid.io/community/. Today we have an
> active contributor base (a typical release has ~40 contributors) and
> mailing list.
> 
> === Core Developers ===
> 
> Druid enjoys good 

[DISCUSS] Druid incubation proposal

[Gian Merlino]

Hi all,

I would like to open up a discussion about incubating Druid at Apache. I've
included a proposal in this mail and have also posted a draft at
https://wiki.apache.org/incubator/DruidProposal. More information about
Druid is also available on our project web site at: http://druid.io/

Thanks for your consideration!

Gian

= 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"
link from the project page: http://druid.io/community/. Today we have an
active contributor base (a typical release has ~40 contributors) and
mailing list.

=== Core Developers ===

Druid enjoys good diversity of committer affiliation. The most active
developers over the past year are affiliated with four different companies:
Imply, Metamarkets, Yahoo, and Hortonworks. Many Druid committers are also
committers on other ASF projects as well, including Apache Airflow, Apache
Curator, and Apache Calcite. The original developers of Druid remain
involved in the project.

=== Alignment ===

Druid's current governance structure is Apache-inspired with a PMC and
committers chosen by a meritocratic process. Additionally, Druid integrates
with a number of other Apache projects, including Kafka, Hadoop, Hive,
Calcite, Superset (incubating), Spark, Curator, and !ZooKeeper.

== Known Risks ==

=== Orphaned products ===

The risk of Druid becoming orphaned is low, due to a diverse committer base
that is invested in the future of the project.

=== Inexperience with Open Source ===

Druid's core developers have been running it as a community-oriented open
source project for some time now, and many of them are committers on other
open source projects as