Re: [RESULTS][VOTE] Accept Doris into the Apache Incubator

[Dave Fisher]

Hi -

Some of the initial steps are completed and I submitted INFRA-16786 
<https://issues.apache.org/jira/browse/INFRA-16786> Setup DNS, LDAP for the new 
podling Apache Doris

We are currently in this step: 
https://incubator.apache.org/guides/mentor.html#resources

Once Infra completes the JIRA I will request the mailing lists. Once those 
exist I will send out information to all of the initial committers and mentors.

Regards,
Dave


> On Jul 17, 2018, at 9:45 PM, Dave Fisher  wrote:
> 
> Hi Li, De,
> 
> I have a couple of administrative steps to do including sending the initial 
> committers a list.
> 
> I’ll do this during my morning in 12 hours. If Luke or Willem wish they can 
> start. Tasks are here: 
> https://incubator.apache.org/policy/incubation.html#setting_up_a_new_podling
> 
> The fourth bullet is special since this will be a github transfer.
> 
> Please review ICLA, but the process is easier if you wait to submit them to 
> the secretary until the mentors complete initial setup.
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
>> On Jul 17, 2018, at 7:42 PM, Li,De(BDG)  wrote:
>> 
>> Hi Dave,
>> 
>> What should we do next? Can you give me a to do list or something?
>> 
>> Best Regards,
>> Reed
>> 
>> 
>> On 2018/7/13 上午10:07， "Li,De(BDG)" mailto:l...@baidu.com>> 
>> wrote:
>> 
>> That’s great, thank you, Dave, thank everyone for your support.
>> 
>> On 2018/7/13 上午6:17， "Dave Fisher" 
>> mailto:dave2w...@comcast.net>> wrote:
>> 
>> Hi -
>> 
>> Welcome Doris to the Apache Incubator!
>> 
>> The vote passes with 8 +1 (binding votes) and 6 +1 (non-binding votes)
>> 
>> Binding votes:
>> Dave Fisher
>> Bertrand Delacretaz
>> Timothy Chen
>> Matt Sicker
>> Willem Jiang
>> Jean-Baptiste Onofré
>> Kevin A. McGrail
>> Han Luke
>> 
>> Non-binding votes:
>> Sijie Guo
>> Zhongyi Tan
>> Charith Elvitigala
>> Xin Wang
>> 吴晟 Sheng Wu
>> Jianru Tong
>> 
>> The VOTE thread archive.
>> https://lists.apache.org/thread.html/916a2249a78bd78b77ded01d42fe932db1b8c3a3c795038128e58ced@%3Cgeneral.incubator.apache.org%3E
>> 
>> Regards,
>> Dave
>> 
>> On Jul 11, 2018, at 4:31 PM, Han Luke 
>> mailto:luke...@gmail.com>> wrote:
>> 
>> +1 binding
>> 
>> 
>> From: Timothy Chen mailto:tnac...@gmail.com>>
>> Sent: Friday, July 6, 2018 5:19:43 PM
>> To: general@incubator.apache.org<mailto:general@incubator.apache.org>
>> Subject: Re: [VOTE] Accept Doris into the Apache Incubator
>> 
>> +1 (binding)
>> 
>> Been following the discussions and knowing the mentors I believe the team
>> can continue to improve and learn how the Apache way works.
>> 
>> Tim
>> On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz <
>> bdelacre...@codeconsult.ch<mailto:bdelacre...@codeconsult.ch>> wrote:
>> 
>> On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG) 
>> mailto:l...@baidu.com>> wrote:
>> ...None of them are affiliated with Baidu Inc., just initial committers
>> are...
>> 
>> Ok, thanks for clarifying!
>> 
>> Here's my +1
>> 
>> -Bertrand
>> 
>> -
>> To unsubscribe, e-mail: 
>> general-unsubscr...@incubator.apache.org<mailto:general-unsubscr...@incubator.apache.org>
>> For additional commands, e-mail: 
>> general-h...@incubator.apache.org<mailto:general-h...@incubator.apache.org>
>> 
>> 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: [RESULTS][VOTE] Accept Doris into the Apache Incubator

[Dave Fisher]

Hi Li, De,

I have a couple of administrative steps to do including sending the initial 
committers a list.

I’ll do this during my morning in 12 hours. If Luke or Willem wish they can 
start. Tasks are here: 
https://incubator.apache.org/policy/incubation.html#setting_up_a_new_podling

The fourth bullet is special since this will be a github transfer.

Please review ICLA, but the process is easier if you wait to submit them to the 
secretary until the mentors complete initial setup.

Regards,
Dave

Sent from my iPhone

> On Jul 17, 2018, at 7:42 PM, Li,De(BDG)  wrote:
> 
> Hi Dave,
> 
> What should we do next? Can you give me a to do list or something?
> 
> Best Regards,
> Reed
> 
> 
> On 2018/7/13 上午10:07， "Li,De(BDG)" mailto:l...@baidu.com>> 
> wrote:
> 
> That’s great, thank you, Dave, thank everyone for your support.
> 
> On 2018/7/13 上午6:17， "Dave Fisher" 
> mailto:dave2w...@comcast.net>> wrote:
> 
> Hi -
> 
> Welcome Doris to the Apache Incubator!
> 
> The vote passes with 8 +1 (binding votes) and 6 +1 (non-binding votes)
> 
> Binding votes:
> Dave Fisher
> Bertrand Delacretaz
> Timothy Chen
> Matt Sicker
> Willem Jiang
> Jean-Baptiste Onofré
> Kevin A. McGrail
> Han Luke
> 
> Non-binding votes:
> Sijie Guo
> Zhongyi Tan
> Charith Elvitigala
> Xin Wang
> 吴晟 Sheng Wu
> Jianru Tong
> 
> The VOTE thread archive.
> https://lists.apache.org/thread.html/916a2249a78bd78b77ded01d42fe932db1b8c3a3c795038128e58ced@%3Cgeneral.incubator.apache.org%3E
> 
> Regards,
> Dave
> 
> On Jul 11, 2018, at 4:31 PM, Han Luke 
> mailto:luke...@gmail.com>> wrote:
> 
> +1 binding
> 
> ________
> From: Timothy Chen mailto:tnac...@gmail.com>>
> Sent: Friday, July 6, 2018 5:19:43 PM
> To: general@incubator.apache.org<mailto:general@incubator.apache.org>
> Subject: Re: [VOTE] Accept Doris into the Apache Incubator
> 
> +1 (binding)
> 
> Been following the discussions and knowing the mentors I believe the team
> can continue to improve and learn how the Apache way works.
> 
> Tim
> On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz <
> bdelacre...@codeconsult.ch<mailto:bdelacre...@codeconsult.ch>> wrote:
> 
> On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG) 
> mailto:l...@baidu.com>> wrote:
> ...None of them are affiliated with Baidu Inc., just initial committers
> are...
> 
> Ok, thanks for clarifying!
> 
> Here's my +1
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: 
> general-unsubscr...@incubator.apache.org<mailto:general-unsubscr...@incubator.apache.org>
> For additional commands, e-mail: 
> general-h...@incubator.apache.org<mailto:general-h...@incubator.apache.org>
> 
> 
> 

Re: [RESULTS][VOTE] Accept Doris into the Apache Incubator

[Li,De(BDG)]

Hi Dave,

What should we do next? Can you give me a to do list or something?

Best Regards,
Reed


On 2018/7/13 上午10:07， "Li,De(BDG)" mailto:l...@baidu.com>> 
wrote:

That’s great, thank you, Dave, thank everyone for your support.

On 2018/7/13 上午6:17， "Dave Fisher" 
mailto:dave2w...@comcast.net>> wrote:

Hi -

Welcome Doris to the Apache Incubator!

The vote passes with 8 +1 (binding votes) and 6 +1 (non-binding votes)

Binding votes:
Dave Fisher
Bertrand Delacretaz
Timothy Chen
Matt Sicker
Willem Jiang
Jean-Baptiste Onofré
Kevin A. McGrail
Han Luke

Non-binding votes:
Sijie Guo
Zhongyi Tan
Charith Elvitigala
Xin Wang
吴晟 Sheng Wu
Jianru Tong

The VOTE thread archive.
https://lists.apache.org/thread.html/916a2249a78bd78b77ded01d42fe932db1b8c3a3c795038128e58ced@%3Cgeneral.incubator.apache.org%3E

Regards,
Dave

On Jul 11, 2018, at 4:31 PM, Han Luke 
mailto:luke...@gmail.com>> wrote:

+1 binding


From: Timothy Chen mailto:tnac...@gmail.com>>
Sent: Friday, July 6, 2018 5:19:43 PM
To: general@incubator.apache.org<mailto:general@incubator.apache.org>
Subject: Re: [VOTE] Accept Doris into the Apache Incubator

+1 (binding)

Been following the discussions and knowing the mentors I believe the team
can continue to improve and learn how the Apache way works.

Tim
On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz <
bdelacre...@codeconsult.ch<mailto:bdelacre...@codeconsult.ch>> wrote:

On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG) 
mailto:l...@baidu.com>> wrote:
...None of them are affiliated with Baidu Inc., just initial committers
are...

Ok, thanks for clarifying!

Here's my +1

-Bertrand

-
To unsubscribe, e-mail: 
general-unsubscr...@incubator.apache.org<mailto:general-unsubscr...@incubator.apache.org>
For additional commands, e-mail: 
general-h...@incubator.apache.org<mailto:general-h...@incubator.apache.org>

Re: [RESULTS][VOTE] Accept Doris into the Apache Incubator

[Tan,Zhongyi]

thanks


在 2018年7月12日，15:18，Dave Fisher 
mailto:dave2w...@comcast.net>> 写道：

Hi -

Welcome Doris to the Apache Incubator!

The vote passes with 8 +1 (binding votes) and 6 +1 (non-binding votes)

Binding votes:
Dave Fisher
Bertrand Delacretaz
Timothy Chen
Matt Sicker
Willem Jiang
Jean-Baptiste Onofré
Kevin A. McGrail
Han Luke

Non-binding votes:
Sijie Guo
Zhongyi Tan
Charith Elvitigala
Xin Wang
吴晟 Sheng Wu
Jianru Tong

The VOTE thread archive.
https://lists.apache.org/thread.html/916a2249a78bd78b77ded01d42fe932db1b8c3a3c795038128e58ced@%3Cgeneral.incubator.apache.org%3E

Regards,
Dave

On Jul 11, 2018, at 4:31 PM, Han Luke 
mailto:luke...@gmail.com>> wrote:

+1 binding


From: Timothy Chen mailto:tnac...@gmail.com>>
Sent: Friday, July 6, 2018 5:19:43 PM
To: general@incubator.apache.org<mailto:general@incubator.apache.org>
Subject: Re: [VOTE] Accept Doris into the Apache Incubator

+1 (binding)

Been following the discussions and knowing the mentors I believe the team
can continue to improve and learn how the Apache way works.

Tim
On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz <
bdelacre...@codeconsult.ch<mailto:bdelacre...@codeconsult.ch>> wrote:

On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG) 
mailto:l...@baidu.com>> wrote:
...None of them are affiliated with Baidu Inc., just initial committers
are...

Ok, thanks for clarifying!

Here's my +1

-Bertrand

-
To unsubscribe, e-mail: 
general-unsubscr...@incubator.apache.org<mailto:general-unsubscr...@incubator.apache.org>
For additional commands, e-mail: 
general-h...@incubator.apache.org<mailto:general-h...@incubator.apache.org>

Re: [RESULTS][VOTE] Accept Doris into the Apache Incubator

[Li,De(BDG)]

That’s great, thank you, Dave, thank everyone for your support.

On 2018/7/13 上午6:17， "Dave Fisher" 
mailto:dave2w...@comcast.net>> wrote:

Hi -

Welcome Doris to the Apache Incubator!

The vote passes with 8 +1 (binding votes) and 6 +1 (non-binding votes)

Binding votes:
Dave Fisher
Bertrand Delacretaz
Timothy Chen
Matt Sicker
Willem Jiang
Jean-Baptiste Onofré
Kevin A. McGrail
Han Luke

Non-binding votes:
Sijie Guo
Zhongyi Tan
Charith Elvitigala
Xin Wang
吴晟 Sheng Wu
Jianru Tong

The VOTE thread archive.
https://lists.apache.org/thread.html/916a2249a78bd78b77ded01d42fe932db1b8c3a3c795038128e58ced@%3Cgeneral.incubator.apache.org%3E

Regards,
Dave

On Jul 11, 2018, at 4:31 PM, Han Luke 
mailto:luke...@gmail.com>> wrote:

+1 binding


From: Timothy Chen mailto:tnac...@gmail.com>>
Sent: Friday, July 6, 2018 5:19:43 PM
To: general@incubator.apache.org<mailto:general@incubator.apache.org>
Subject: Re: [VOTE] Accept Doris into the Apache Incubator

+1 (binding)

Been following the discussions and knowing the mentors I believe the team
can continue to improve and learn how the Apache way works.

Tim
On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz <
bdelacre...@codeconsult.ch<mailto:bdelacre...@codeconsult.ch>> wrote:

On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG) 
mailto:l...@baidu.com>> wrote:
...None of them are affiliated with Baidu Inc., just initial committers
are...

Ok, thanks for clarifying!

Here's my +1

-Bertrand

-
To unsubscribe, e-mail: 
general-unsubscr...@incubator.apache.org<mailto:general-unsubscr...@incubator.apache.org>
For additional commands, e-mail: 
general-h...@incubator.apache.org<mailto:general-h...@incubator.apache.org>

[RESULTS][VOTE] Accept Doris into the Apache Incubator

[Dave Fisher]

Hi -

Welcome Doris to the Apache Incubator!

The vote passes with 8 +1 (binding votes) and 6 +1 (non-binding votes)

Binding votes:
Dave Fisher
Bertrand Delacretaz
Timothy Chen
Matt Sicker
Willem Jiang
Jean-Baptiste Onofré
Kevin A. McGrail
Han Luke

Non-binding votes:
Sijie Guo
Zhongyi Tan
Charith Elvitigala
Xin Wang
吴晟 Sheng Wu
Jianru Tong

The VOTE thread archive.
https://lists.apache.org/thread.html/916a2249a78bd78b77ded01d42fe932db1b8c3a3c795038128e58ced@%3Cgeneral.incubator.apache.org%3E

Regards,
Dave

> On Jul 11, 2018, at 4:31 PM, Han Luke  wrote:
> 
> +1 binding
> 
> 
> From: Timothy Chen 
> Sent: Friday, July 6, 2018 5:19:43 PM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Accept Doris into the Apache Incubator
> 
> +1 (binding)
> 
> Been following the discussions and knowing the mentors I believe the team
> can continue to improve and learn how the Apache way works.
> 
> Tim
> On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
> 
>> On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG)  wrote:
>>> ...None of them are affiliated with Baidu Inc., just initial committers
>> are...
>> 
>> Ok, thanks for clarifying!
>> 
>> Here's my +1
>> 
>> -Bertrand
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Accept Doris into the Apache Incubator

[Han Luke]

+1 binding


From: Timothy Chen 
Sent: Friday, July 6, 2018 5:19:43 PM
To: general@incubator.apache.org
Subject: Re: [VOTE] Accept Doris into the Apache Incubator

+1 (binding)

Been following the discussions and knowing the mentors I believe the team
can continue to improve and learn how the Apache way works.

Tim
On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG)  wrote:
> > ...None of them are affiliated with Baidu Inc., just initial committers
> are...
>
> Ok, thanks for clarifying!
>
> Here's my +1
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Doris into the Apache Incubator

[Tan,Zhongyi]

Hi, dave,
Could this vote be closed ?
It seems that it has passed half a week since July 6th,
Thanks.


发件人: Dave Fisher mailto:dave2w...@comcast.net>>
答复: mailto:general@incubator.apache.org>>
日期: 2018年7月6日 星期五 上午3:22
至: mailto:general@incubator.apache.org>>
主题: [VOTE] Accept Doris into the Apache Incubator

Hi All,

I would like to start a VOTE to bring the Doris project as an Apache incubator 
podling.

The ASF voting rules are described:

https://www.apache.org/foundation/voting.html

A vote for accepting a new Apache Incubator podling is a majority vote for 
which only Incubator PMC member votes are binding.

This vote will run for at least 72 hours. Please VOTE as follows
[] +1 Accept Doris into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept Doris into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

https://wiki.apache.org/incubator/DorisProposal

Best regards,
Dave

= Apache Doris =

== Abstract ==

Doris is a MPP-based interactive SQL data warehousing for reporting and 
analysis.

== Proposal ==

We propose to contribute the Doris codebase and associated artifacts (e.g. 
documentation, web-site content etc.) to the Apache Software Foundation, and 
aim to build an open community around Doris’s continued development in the 
‘Apache Way’.

=== Overview of Doris ===

Doris’s implementation consists of two daemons: Frontend (FE) and Backend (BE).

**Frontend daemon** consists of query coordinator and catalog manager. Query 
coordinator is responsible for receiving users’ sql queries, compiling queries 
and managing queries execution. Catalog manager is responsible for managing 
metadata such as databases, tables, partitions, replicas and etc. Several 
frontend daemons could be deployed to guarantee fault-tolerance, and load 
balancing.

**Backend daemon** stores the data and executes the query fragments. Many 
backend daemons could also be deployed to provide scalability and 
fault-tolerance.

A typical Doris cluster generally composes of several frontend daemons and 
dozens to hundreds of backend daemons.

Users can use MySQL client tools to connect any frontend daemon to submit SQL 
query. Frontend receives the query and compiles it into query plans executable 
by the Backend. Then Frontend sends the query plan fragments to Backend. 
Backend will build a query execution DAG. Data is fetched and pipelined into 
the DAG. The final result response is sent to client via Frontend. The 
distribution of query fragment execution takes minimizing data movement and 
maximizing scan locality as the main goal.

== Background ==

At Baidu, Prior to Doris, different tools were deployed to solve diverse 
requirements in many ways. And when a use case requires the simultaneous 
availability of capabilities that cannot all be provided by a single tool, 
users were forced to build hybrid architectures that stitch multiple tools 
together, but we believe that they shouldn’t need to accept such inherent 
complexity. A storage system built to provide great performance across a broad 
range of workloads provides a more elegant solution to the problems that hybrid 
architectures aim to solve. Doris is the solution.

Doris is designed to be a simple and single tightly coupled system, not 
depending on other systems. Doris provides high concurrent low latency point 
query performance, but also provides high throughput queries of ad-hoc 
analysis. Doris provides bulk-batch data loading, but also provides near 
real-time mini-batch data loading. Doris also provides high availability, 
reliability, fault tolerance, and scalability.

== Rationale ==

Doris mainly integrates the technology of Google Mesa and Apache Impala.

Mesa is a highly scalable analytic data storage system that stores critical 
measurement data related to Google's Internet advertising business. Mesa is 
designed to satisfy complex and challenging set of users’ and systems’ 
requirements, including near real-time data ingestion and query ability, as 
well as high availability, reliability, fault tolerance, and scalability for 
large data and query volumes.

Impala is a modern, open-source MPP SQL engine architected from the ground up 
for the Hadoop data processing environment. At present, by virtue of its 
superior performance and rich functionality， Impala has been comparable to many 
commercial MPP database query engine. Mesa can satisfy the needs of many of our 
storage requirements, however Mesa itself does not provide a SQL query engine; 
Impala is a very good MPP SQL query engine, but the lack of a perfect 
distributed storage engine. So in the end we chose the combination of these two 
technologies.

Learning from Mesa’s data model, we developed a distributed storage engine. 
Unlike Mesa, this storage engine does not rely on any distributed file system. 
Then we deeply integrate this storage engine with Impala query engine. Query 
compiling, query execution c

Re: [VOTE] Accept Doris into the Apache Incubator

[Kevin A. McGrail]

+1 Binding

A minor note:  Things like MPP should be spelled out at least once.  Your
proposal was technical and it helps if you think about trying to explain it
to an engineer who doesn't now Impala or Mesos or SQL, etc.

--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Thu, Jul 5, 2018 at 3:22 PM, Dave Fisher  wrote:

> Hi All,
>
> I would like to start a VOTE to bring the Doris project as an Apache
> incubator podling.
>
> The ASF voting rules are described:
>
> https://www.apache.org/foundation/voting.html
>
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which
> only Incubator PMC member votes are binding.
>
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Doris into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Doris into the Apache Incubator because ...
>
> The proposal is listed below, but you can also access it on the wiki:
>
> https://wiki.apache.org/incubator/DorisProposal
>
> Best regards,
> Dave
>
> = Apache Doris =
>
> == Abstract ==
>
> Doris is a MPP-based interactive SQL data warehousing for reporting and
> analysis.
>
> == Proposal ==
>
> We propose to contribute the Doris codebase and associated artifacts (e.g.
> documentation, web-site content etc.) to the Apache Software Foundation,
> and aim to build an open community around Doris’s continued development in
> the ‘Apache Way’.
>
> === Overview of Doris ===
>
> Doris’s implementation consists of two daemons: Frontend (FE) and Backend
> (BE).
>
> **Frontend daemon** consists of query coordinator and catalog manager.
> Query coordinator is responsible for receiving users’ sql queries,
> compiling queries and managing queries execution. Catalog manager is
> responsible for managing metadata such as databases, tables, partitions,
> replicas and etc. Several frontend daemons could be deployed to guarantee
> fault-tolerance, and load balancing.
>
> **Backend daemon** stores the data and executes the query fragments. Many
> backend daemons could also be deployed to provide scalability and
> fault-tolerance.
>
> A typical Doris cluster generally composes of several frontend daemons and
> dozens to hundreds of backend daemons.
>
> Users can use MySQL client tools to connect any frontend daemon to submit
> SQL query. Frontend receives the query and compiles it into query plans
> executable by the Backend. Then Frontend sends the query plan fragments to
> Backend. Backend will build a query execution DAG. Data is fetched and
> pipelined into the DAG. The final result response is sent to client via
> Frontend. The distribution of query fragment execution takes minimizing
> data movement and maximizing scan locality as the main goal.
>
> == Background ==
>
> At Baidu, Prior to Doris, different tools were deployed to solve diverse
> requirements in many ways. And when a use case requires the simultaneous
> availability of capabilities that cannot all be provided by a single tool,
> users were forced to build hybrid architectures that stitch multiple tools
> together, but we believe that they shouldn’t need to accept such inherent
> complexity. A storage system built to provide great performance across a
> broad range of workloads provides a more elegant solution to the problems
> that hybrid architectures aim to solve. Doris is the solution.
>
> Doris is designed to be a simple and single tightly coupled system, not
> depending on other systems. Doris provides high concurrent low latency
> point query performance, but also provides high throughput queries of
> ad-hoc analysis. Doris provides bulk-batch data loading, but also provides
> near real-time mini-batch data loading. Doris also provides high
> availability, reliability, fault tolerance, and scalability.
>
> == Rationale ==
>
> Doris mainly integrates the technology of Google Mesa and Apache Impala.
>
> Mesa is a highly scalable analytic data storage system that stores
> critical measurement data related to Google's Internet advertising
> business. Mesa is designed to satisfy complex and challenging set of users’
> and systems’ requirements, including near real-time data ingestion and
> query ability, as well as high availability, reliability, fault tolerance,
> and scalability for large data and query volumes.
>
> Impala is a modern, open-source MPP SQL engine architected from the ground
> up for the Hadoop data processing environment. At present, by virtue of its
> superior performance and rich functionality， Impala has been comparable to
> many commercial MPP database query engine. Mesa can satisfy the needs of
> many of our storage requirements, however Mesa itself does not provide a
> SQL query engine; Impala is a very good MPP SQL query engine, but the lack
> of a perfect distributed storage engine. So in the end we chose the
> combination of these two technologies.
>
> Learning from Mesa’s data mo

Re: [VOTE] Accept Doris into the Apache Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On 05/07/2018 21:22, Dave Fisher wrote:
> Hi All,
> 
> I would like to start a VOTE to bring the Doris project as an Apache
> incubator podling.
> 
> The ASF voting rules are described:
> 
> https://www.apache.org/foundation/voting.html
> 
> A vote for accepting a new Apache Incubator podling is a majority vote
> for which only Incubator PMC member votes are binding.
> 
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Doris into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Doris into the Apache Incubator because ...
> 
> The proposal is listed below, but you can also access it on the wiki:
> 
> https://wiki.apache.org/incubator/DorisProposal
> 
> Best regards,
> Dave
> 
> = Apache Doris =
> 
> == Abstract ==
> 
> Doris is a MPP-based interactive SQL data warehousing for reporting and
> analysis. 
> 
> == Proposal ==
> 
> We propose to contribute the Doris codebase and associated artifacts
> (e.g. documentation, web-site content etc.) to the Apache Software
> Foundation, and aim to build an open community around Doris’s continued
> development in the ‘Apache Way’.
> 
> === Overview of Doris ===
> 
> Doris’s implementation consists of two daemons: Frontend (FE) and
> Backend (BE).
> 
> **Frontend daemon** consists of query coordinator and catalog manager.
> Query coordinator is responsible for receiving users’ sql queries,
> compiling queries and managing queries execution. Catalog manager is
> responsible for managing metadata such as databases, tables, partitions,
> replicas and etc. Several frontend daemons could be deployed to
> guarantee fault-tolerance, and load balancing.
> 
> **Backend daemon** stores the data and executes the query fragments.
> Many backend daemons could also be deployed to provide scalability and
> fault-tolerance.
> 
> A typical Doris cluster generally composes of several frontend daemons
> and dozens to hundreds of backend daemons.
> 
> Users can use MySQL client tools to connect any frontend daemon to
> submit SQL query. Frontend receives the query and compiles it into query
> plans executable by the Backend. Then Frontend sends the query plan
> fragments to Backend. Backend will build a query execution DAG. Data is
> fetched and pipelined into the DAG. The final result response is sent to
> client via Frontend. The distribution of query fragment execution takes
> minimizing data movement and maximizing scan locality as the main goal. 
> 
> == Background ==
> 
> At Baidu, Prior to Doris, different tools were deployed to solve diverse
> requirements in many ways. And when a use case requires the simultaneous
> availability of capabilities that cannot all be provided by a single
> tool, users were forced to build hybrid architectures that stitch
> multiple tools together, but we believe that they shouldn’t need to
> accept such inherent complexity. A storage system built to provide great
> performance across a broad range of workloads provides a more elegant
> solution to the problems that hybrid architectures aim to solve. Doris
> is the solution. 
> 
> Doris is designed to be a simple and single tightly coupled system, not
> depending on other systems. Doris provides high concurrent low latency
> point query performance, but also provides high throughput queries of
> ad-hoc analysis. Doris provides bulk-batch data loading, but also
> provides near real-time mini-batch data loading. Doris also provides
> high availability, reliability, fault tolerance, and scalability.
> 
> == Rationale ==
> 
> Doris mainly integrates the technology of Google Mesa and Apache Impala. 
> 
> Mesa is a highly scalable analytic data storage system that stores
> critical measurement data related to Google's Internet advertising
> business. Mesa is designed to satisfy complex and challenging set of
> users’ and systems’ requirements, including near real-time data
> ingestion and query ability, as well as high availability, reliability,
> fault tolerance, and scalability for large data and query volumes. 
> 
> Impala is a modern, open-source MPP SQL engine architected from the
> ground up for the Hadoop data processing environment. At present, by
> virtue of its superior performance and rich functionality， Impala has
> been comparable to many commercial MPP database query engine. Mesa can
> satisfy the needs of many of our storage requirements, however Mesa
> itself does not provide a SQL query engine; Impala is a very good MPP
> SQL query engine, but the lack of a perfect distributed storage engine.
> So in the end we chose the combination of these two technologies.
> 
> Learning from Mesa’s data model, we developed a distributed storage
> engine. Unlike Mesa, this storage engine does not rely on any
> distributed file system. Then we deeply integrate this storage engine
> with Impala query engine. Query compiling, query execution coordination
> and catalog management of storage engine are integrated to be frontend
> daemon; query

Re: [VOTE] Accept Doris into the Apache Incubator

[???? Sheng Wu]

My +1 no-binding.


Welcome to join the community. Interesting project. 


--
Sheng Wu
Apache SkyWalking 


 




-- Original --
From:  "Matt Sicker";
Date:  Sun, Jul 8, 2018 03:22 AM
To:  "general";

Subject:  Re: [VOTE] Accept Doris into the Apache Incubator



+1 (binding)

Sounds like a really interesting project. I hope to see more PPMC members
from outside Baidu over time of course!

On Fri, 6 Jul 2018 at 04:20, Timothy Chen  wrote:

> +1 (binding)
>
> Been following the discussions and knowing the mentors I believe the team
> can continue to improve and learn how the Apache way works.
>
> Tim
> On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
>
> > On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG)  wrote:
> > > ...None of them are affiliated with Baidu Inc., just initial committers
> > are...
> >
> > Ok, thanks for clarifying!
> >
> > Here's my +1
> >
> > -Bertrand
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>


-- 
Matt Sicker 

Re: [VOTE] Accept Doris into the Apache Incubator

[Willem Jiang]

+1 (binding)



Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Jul 6, 2018 at 3:22 AM, Dave Fisher  wrote:

> Hi All,
>
> I would like to start a VOTE to bring the Doris project as an Apache
> incubator podling.
>
> The ASF voting rules are described:
>
> https://www.apache.org/foundation/voting.html
>
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which
> only Incubator PMC member votes are binding.
>
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Doris into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Doris into the Apache Incubator because ...
>
> The proposal is listed below, but you can also access it on the wiki:
>
> https://wiki.apache.org/incubator/DorisProposal
>
> Best regards,
> Dave
>
> = Apache Doris =
>
> == Abstract ==
>
> Doris is a MPP-based interactive SQL data warehousing for reporting and
> analysis.
>
> == Proposal ==
>
> We propose to contribute the Doris codebase and associated artifacts (e.g.
> documentation, web-site content etc.) to the Apache Software Foundation,
> and aim to build an open community around Doris’s continued development in
> the ‘Apache Way’.
>
> === Overview of Doris ===
>
> Doris’s implementation consists of two daemons: Frontend (FE) and Backend
> (BE).
>
> **Frontend daemon** consists of query coordinator and catalog manager.
> Query coordinator is responsible for receiving users’ sql queries,
> compiling queries and managing queries execution. Catalog manager is
> responsible for managing metadata such as databases, tables, partitions,
> replicas and etc. Several frontend daemons could be deployed to guarantee
> fault-tolerance, and load balancing.
>
> **Backend daemon** stores the data and executes the query fragments. Many
> backend daemons could also be deployed to provide scalability and
> fault-tolerance.
>
> A typical Doris cluster generally composes of several frontend daemons and
> dozens to hundreds of backend daemons.
>
> Users can use MySQL client tools to connect any frontend daemon to submit
> SQL query. Frontend receives the query and compiles it into query plans
> executable by the Backend. Then Frontend sends the query plan fragments to
> Backend. Backend will build a query execution DAG. Data is fetched and
> pipelined into the DAG. The final result response is sent to client via
> Frontend. The distribution of query fragment execution takes minimizing
> data movement and maximizing scan locality as the main goal.
>
> == Background ==
>
> At Baidu, Prior to Doris, different tools were deployed to solve diverse
> requirements in many ways. And when a use case requires the simultaneous
> availability of capabilities that cannot all be provided by a single tool,
> users were forced to build hybrid architectures that stitch multiple tools
> together, but we believe that they shouldn’t need to accept such inherent
> complexity. A storage system built to provide great performance across a
> broad range of workloads provides a more elegant solution to the problems
> that hybrid architectures aim to solve. Doris is the solution.
>
> Doris is designed to be a simple and single tightly coupled system, not
> depending on other systems. Doris provides high concurrent low latency
> point query performance, but also provides high throughput queries of
> ad-hoc analysis. Doris provides bulk-batch data loading, but also provides
> near real-time mini-batch data loading. Doris also provides high
> availability, reliability, fault tolerance, and scalability.
>
> == Rationale ==
>
> Doris mainly integrates the technology of Google Mesa and Apache Impala.
>
> Mesa is a highly scalable analytic data storage system that stores
> critical measurement data related to Google's Internet advertising
> business. Mesa is designed to satisfy complex and challenging set of users’
> and systems’ requirements, including near real-time data ingestion and
> query ability, as well as high availability, reliability, fault tolerance,
> and scalability for large data and query volumes.
>
> Impala is a modern, open-source MPP SQL engine architected from the ground
> up for the Hadoop data processing environment. At present, by virtue of its
> superior performance and rich functionality， Impala has been comparable to
> many commercial MPP database query engine. Mesa can satisfy the needs of
> many of our storage requirements, however Mesa itself does not provide a
> SQL query engine; Impala is a very good MPP SQL query engine, but the lack
> of a perfect distributed storage engine. So in the end we chose the
> combination of these two technologies.
>
> Learning from Mesa’s data model, we developed a distributed storage
> engine. Unlike Mesa, this storage engine does not rely on any distributed
> file system. Then we deeply integrate this storage engine with Impala query
> engine. Query compiling, query execution coordination and catalog
> management of storage engine are integrated to be 

Re: [VOTE] Accept Doris into the Apache Incubator

[Matt Sicker]

+1 (binding)

Sounds like a really interesting project. I hope to see more PPMC members
from outside Baidu over time of course!

On Fri, 6 Jul 2018 at 04:20, Timothy Chen  wrote:

> +1 (binding)
>
> Been following the discussions and knowing the mentors I believe the team
> can continue to improve and learn how the Apache way works.
>
> Tim
> On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
>
> > On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG)  wrote:
> > > ...None of them are affiliated with Baidu Inc., just initial committers
> > are...
> >
> > Ok, thanks for clarifying!
> >
> > Here's my +1
> >
> > -Bertrand
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>


-- 
Matt Sicker 

Re: [VOTE] Accept Doris into the Apache Incubator

[Timothy Chen]

+1 (binding)

Been following the discussions and knowing the mentors I believe the team
can continue to improve and learn how the Apache way works.

Tim
On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG)  wrote:
> > ...None of them are affiliated with Baidu Inc., just initial committers
> are...
>
> Ok, thanks for clarifying!
>
> Here's my +1
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Doris into the Apache Incubator

[Bertrand Delacretaz]

On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG)  wrote:
> ...None of them are affiliated with Baidu Inc., just initial committers are...

Ok, thanks for clarifying!

Here's my +1

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Doris into the Apache Incubator

[Li,De(BDG)]

None of them are affiliated with Baidu Inc., just initial committers are.

Best Regards,
Reed

On 2018/7/6 下午4:04， "Bertrand Delacretaz" 
wrote:

>Hi,
>
>On Thu, Jul 5, 2018 at 9:22 PM Dave Fisher  wrote:
>> The initial committers are employees of Baidu Inc..
>...
>> === Nominated Mentors ===
>>
>>  * Luke Han, luke...@apache.org
>>  * Dave Fisher, w...@apache.org
>>  * Willem Jiang, ningji...@apache.org ...
>
>Are the mentors also affiliated with Baidu Inc.. ?
>
>-Bertrand
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Doris into the Apache Incubator

[Bertrand Delacretaz]

Hi,

On Thu, Jul 5, 2018 at 9:22 PM Dave Fisher  wrote:
> The initial committers are employees of Baidu Inc..
...
> === Nominated Mentors ===
>
>  * Luke Han, luke...@apache.org
>  * Dave Fisher, w...@apache.org
>  * Willem Jiang, ningji...@apache.org ...

Are the mentors also affiliated with Baidu Inc.. ?

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Doris into the Apache Incubator

[Tong,Jianru]

+1 （non binding）

On 2018/07/05 19:22:19, Dave Fisher  wrote: 
> Hi All,> 
> 
> I would like to start a VOTE to bring the Doris project as an Apache 
> incubator podling.> 
> 
> The ASF voting rules are described:> 
> 
> https://www.apache.org/foundation/voting.html 
> > 
> 
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which only Incubator PMC member votes are binding.> 
> 
> This vote will run for at least 72 hours. Please VOTE as follows> 
> [] +1 Accept Doris into the Apache Incubator> 
> [] +0 Abstain.> 
> [] -1 Do not accept Doris into the Apache Incubator because ...> 
> 
> The proposal is listed below, but you can also access it on the wiki:> 
> 
> https://wiki.apache.org/incubator/DorisProposal> 
> 
> Best regards,> 
> Dave> 
> 
> = Apache Doris => 
> 
> == Abstract ==> 
> 
> Doris is a MPP-based interactive SQL data warehousing for reporting and 
> analysis.> 
> 
> == Proposal ==> 
> 
> We propose to contribute the Doris codebase and associated artifacts (e.g. 
> documentation, web-site content etc.) to the Apache Software Foundation, and 
> aim to build an open community around Doris’s continued development in the 
> ‘Apache Way’.> 
> 
> === Overview of Doris ===> 
> 
> Doris’s implementation consists of two daemons: Frontend (FE) and Backend 
> (BE).> 
> 
> **Frontend daemon** consists of query coordinator and catalog manager. Query 
> coordinator is responsible for receiving users’ sql queries, compiling 
> queries and managing queries execution. Catalog manager is responsible for 
> managing metadata such as databases, tables, partitions, replicas and etc. 
> Several frontend daemons could be deployed to guarantee fault-tolerance, and 
> load balancing.> 
> 
> **Backend daemon** stores the data and executes the query fragments. Many 
> backend daemons could also be deployed to provide scalability and 
> fault-tolerance.> 
> 
> A typical Doris cluster generally composes of several frontend daemons and 
> dozens to hundreds of backend daemons.> 
> 
> Users can use MySQL client tools to connect any frontend daemon to submit SQL 
> query. Frontend receives the query and compiles it into query plans 
> executable by the Backend. Then Frontend sends the query plan fragments to 
> Backend. Backend will build a query execution DAG. Data is fetched and 
> pipelined into the DAG. The final result response is sent to client via 
> Frontend. The distribution of query fragment execution takes minimizing data 
> movement and maximizing scan locality as the main goal.> 
> 
> == Background ==> 
> 
> At Baidu, Prior to Doris, different tools were deployed to solve diverse 
> requirements in many ways. And when a use case requires the simultaneous 
> availability of capabilities that cannot all be provided by a single tool, 
> users were forced to build hybrid architectures that stitch multiple tools 
> together, but we believe that they shouldn’t need to accept such inherent 
> complexity. A storage system built to provide great performance across a 
> broad range of workloads provides a more elegant solution to the problems 
> that hybrid architectures aim to solve. Doris is the solution.> 
> 
> Doris is designed to be a simple and single tightly coupled system, not 
> depending on other systems. Doris provides high concurrent low latency point 
> query performance, but also provides high throughput queries of ad-hoc 
> analysis. Doris provides bulk-batch data loading, but also provides near 
> real-time mini-batch data loading. Doris also provides high availability, 
> reliability, fault tolerance, and scalability.> 
> 
> == Rationale ==> 
> 
> Doris mainly integrates the technology of Google Mesa and Apache Impala.> 
> 
> Mesa is a highly scalable analytic data storage system that stores critical 
> measurement data related to Google's Internet advertising business. Mesa is 
> designed to satisfy complex and challenging set of users’ and systems’ 
> requirements, including near real-time data ingestion and query ability, as 
> well as high availability, reliability, fault tolerance, and scalability for 
> large data and query volumes.> 
> 
> Impala is a modern, open-source MPP SQL engine architected from the ground up 
> for the Hadoop data processing environment. At present, by virtue of its 
> superior performance and rich functionality， Impala has been comparable to 
> many commercial MPP database query engine. Mesa can satisfy the needs of many 
> of our storage requirements, however Mesa itself does not provide a SQL query 
> engine; Impala is a very good MPP SQL query engine, but the lack of a perfect 
> distributed storage engine. So in the end we chose the combination of these 
> two technologies.> 
> 
> Learning from Mesa’s data model, we developed a distributed storage engine. 
> Unlike Mesa, this storage engine does not rely on any distributed file 
> system. Then we deeply integrate this storage engine with Impala 

Re: [VOTE] Accept Doris into the Apache Incubator

[Xin Wang]

+1

Charith Elvitigala  于2018年7月6日周五 上午9:37写道：

> +1
>
> On Fri, 6 Jul 2018 at 06:21, Tan,Zhongyi  wrote:
>
> > +1 （no binding）
> >
> > 发件人: Dave Fisher mailto:dave2w...@comcast.net>>
> > 答复: mailto:general@incubator.apache.org>>
> > 日期: 2018年7月6日 星期五 上午3:22
> > 至: mailto:general@incubator.apache.org>>
> > 主题: [VOTE] Accept Doris into the Apache Incubator
> >
> > Hi All,
> >
> > I would like to start a VOTE to bring the Doris project as an Apache
> > incubator podling.
> >
> > The ASF voting rules are described:
> >
> > https://www.apache.org/foundation/voting.html
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote
> for
> > which only Incubator PMC member votes are binding.
> >
> > This vote will run for at least 72 hours. Please VOTE as follows
> > [] +1 Accept Doris into the Apache Incubator
> > [] +0 Abstain.
> > [] -1 Do not accept Doris into the Apache Incubator because ...
> >
> > The proposal is listed below, but you can also access it on the wiki:
> >
> > https://wiki.apache.org/incubator/DorisProposal
> >
> > Best regards,
> > Dave
> >
> > = Apache Doris =
> >
> > == Abstract ==
> >
> > Doris is a MPP-based interactive SQL data warehousing for reporting and
> > analysis.
> >
> > == Proposal ==
> >
> > We propose to contribute the Doris codebase and associated artifacts
> (e.g.
> > documentation, web-site content etc.) to the Apache Software Foundation,
> > and aim to build an open community around Doris’s continued development
> in
> > the ‘Apache Way’.
> >
> > === Overview of Doris ===
> >
> > Doris’s implementation consists of two daemons: Frontend (FE) and Backend
> > (BE).
> >
> > **Frontend daemon** consists of query coordinator and catalog manager.
> > Query coordinator is responsible for receiving users’ sql queries,
> > compiling queries and managing queries execution. Catalog manager is
> > responsible for managing metadata such as databases, tables, partitions,
> > replicas and etc. Several frontend daemons could be deployed to guarantee
> > fault-tolerance, and load balancing.
> >
> > **Backend daemon** stores the data and executes the query fragments. Many
> > backend daemons could also be deployed to provide scalability and
> > fault-tolerance.
> >
> > A typical Doris cluster generally composes of several frontend daemons
> and
> > dozens to hundreds of backend daemons.
> >
> > Users can use MySQL client tools to connect any frontend daemon to submit
> > SQL query. Frontend receives the query and compiles it into query plans
> > executable by the Backend. Then Frontend sends the query plan fragments
> to
> > Backend. Backend will build a query execution DAG. Data is fetched and
> > pipelined into the DAG. The final result response is sent to client via
> > Frontend. The distribution of query fragment execution takes minimizing
> > data movement and maximizing scan locality as the main goal.
> >
> > == Background ==
> >
> > At Baidu, Prior to Doris, different tools were deployed to solve diverse
> > requirements in many ways. And when a use case requires the simultaneous
> > availability of capabilities that cannot all be provided by a single
> tool,
> > users were forced to build hybrid architectures that stitch multiple
> tools
> > together, but we believe that they shouldn’t need to accept such inherent
> > complexity. A storage system built to provide great performance across a
> > broad range of workloads provides a more elegant solution to the problems
> > that hybrid architectures aim to solve. Doris is the solution.
> >
> > Doris is designed to be a simple and single tightly coupled system, not
> > depending on other systems. Doris provides high concurrent low latency
> > point query performance, but also provides high throughput queries of
> > ad-hoc analysis. Doris provides bulk-batch data loading, but also
> provides
> > near real-time mini-batch data loading. Doris also provides high
> > availability, reliability, fault tolerance, and scalability.
> >
> > == Rationale ==
> >
> > Doris mainly integrates the technology of Google Mesa and Apache Impala.
> >
> > Mesa is a highly scalable analytic data storage system that stores
> > critical measurement data related to Google's Internet advertising
> > business. Mesa is designed to satisfy complex and challenging set of
> users’
> > and systems’ requirem

Re: [VOTE] Accept Doris into the Apache Incubator

[Charith Elvitigala]

+1

On Fri, 6 Jul 2018 at 06:21, Tan,Zhongyi  wrote:

> +1 （no binding）
>
> 发件人: Dave Fisher mailto:dave2w...@comcast.net>>
> 答复: mailto:general@incubator.apache.org>>
> 日期: 2018年7月6日 星期五 上午3:22
> 至: mailto:general@incubator.apache.org>>
> 主题: [VOTE] Accept Doris into the Apache Incubator
>
> Hi All,
>
> I would like to start a VOTE to bring the Doris project as an Apache
> incubator podling.
>
> The ASF voting rules are described:
>
> https://www.apache.org/foundation/voting.html
>
> A vote for accepting a new Apache Incubator podling is a majority vote for
> which only Incubator PMC member votes are binding.
>
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Doris into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Doris into the Apache Incubator because ...
>
> The proposal is listed below, but you can also access it on the wiki:
>
> https://wiki.apache.org/incubator/DorisProposal
>
> Best regards,
> Dave
>
> = Apache Doris =
>
> == Abstract ==
>
> Doris is a MPP-based interactive SQL data warehousing for reporting and
> analysis.
>
> == Proposal ==
>
> We propose to contribute the Doris codebase and associated artifacts (e.g.
> documentation, web-site content etc.) to the Apache Software Foundation,
> and aim to build an open community around Doris’s continued development in
> the ‘Apache Way’.
>
> === Overview of Doris ===
>
> Doris’s implementation consists of two daemons: Frontend (FE) and Backend
> (BE).
>
> **Frontend daemon** consists of query coordinator and catalog manager.
> Query coordinator is responsible for receiving users’ sql queries,
> compiling queries and managing queries execution. Catalog manager is
> responsible for managing metadata such as databases, tables, partitions,
> replicas and etc. Several frontend daemons could be deployed to guarantee
> fault-tolerance, and load balancing.
>
> **Backend daemon** stores the data and executes the query fragments. Many
> backend daemons could also be deployed to provide scalability and
> fault-tolerance.
>
> A typical Doris cluster generally composes of several frontend daemons and
> dozens to hundreds of backend daemons.
>
> Users can use MySQL client tools to connect any frontend daemon to submit
> SQL query. Frontend receives the query and compiles it into query plans
> executable by the Backend. Then Frontend sends the query plan fragments to
> Backend. Backend will build a query execution DAG. Data is fetched and
> pipelined into the DAG. The final result response is sent to client via
> Frontend. The distribution of query fragment execution takes minimizing
> data movement and maximizing scan locality as the main goal.
>
> == Background ==
>
> At Baidu, Prior to Doris, different tools were deployed to solve diverse
> requirements in many ways. And when a use case requires the simultaneous
> availability of capabilities that cannot all be provided by a single tool,
> users were forced to build hybrid architectures that stitch multiple tools
> together, but we believe that they shouldn’t need to accept such inherent
> complexity. A storage system built to provide great performance across a
> broad range of workloads provides a more elegant solution to the problems
> that hybrid architectures aim to solve. Doris is the solution.
>
> Doris is designed to be a simple and single tightly coupled system, not
> depending on other systems. Doris provides high concurrent low latency
> point query performance, but also provides high throughput queries of
> ad-hoc analysis. Doris provides bulk-batch data loading, but also provides
> near real-time mini-batch data loading. Doris also provides high
> availability, reliability, fault tolerance, and scalability.
>
> == Rationale ==
>
> Doris mainly integrates the technology of Google Mesa and Apache Impala.
>
> Mesa is a highly scalable analytic data storage system that stores
> critical measurement data related to Google's Internet advertising
> business. Mesa is designed to satisfy complex and challenging set of users’
> and systems’ requirements, including near real-time data ingestion and
> query ability, as well as high availability, reliability, fault tolerance,
> and scalability for large data and query volumes.
>
> Impala is a modern, open-source MPP SQL engine architected from the ground
> up for the Hadoop data processing environment. At present, by virtue of its
> superior performance and rich functionality， Impala has been comparable to
> many commercial MPP database query engine. Mesa can satisfy the needs of
> many of our storage requirements, however Mesa itself does not provide a
> SQL query engine

Re: [VOTE] Accept Doris into the Apache Incubator

[Tan,Zhongyi]

+1 （no binding）

发件人: Dave Fisher mailto:dave2w...@comcast.net>>
答复: mailto:general@incubator.apache.org>>
日期: 2018年7月6日 星期五 上午3:22
至: mailto:general@incubator.apache.org>>
主题: [VOTE] Accept Doris into the Apache Incubator

Hi All,

I would like to start a VOTE to bring the Doris project as an Apache incubator 
podling.

The ASF voting rules are described:

https://www.apache.org/foundation/voting.html

A vote for accepting a new Apache Incubator podling is a majority vote for 
which only Incubator PMC member votes are binding.

This vote will run for at least 72 hours. Please VOTE as follows
[] +1 Accept Doris into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept Doris into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

https://wiki.apache.org/incubator/DorisProposal

Best regards,
Dave

= Apache Doris =

== Abstract ==

Doris is a MPP-based interactive SQL data warehousing for reporting and 
analysis.

== Proposal ==

We propose to contribute the Doris codebase and associated artifacts (e.g. 
documentation, web-site content etc.) to the Apache Software Foundation, and 
aim to build an open community around Doris’s continued development in the 
‘Apache Way’.

=== Overview of Doris ===

Doris’s implementation consists of two daemons: Frontend (FE) and Backend (BE).

**Frontend daemon** consists of query coordinator and catalog manager. Query 
coordinator is responsible for receiving users’ sql queries, compiling queries 
and managing queries execution. Catalog manager is responsible for managing 
metadata such as databases, tables, partitions, replicas and etc. Several 
frontend daemons could be deployed to guarantee fault-tolerance, and load 
balancing.

**Backend daemon** stores the data and executes the query fragments. Many 
backend daemons could also be deployed to provide scalability and 
fault-tolerance.

A typical Doris cluster generally composes of several frontend daemons and 
dozens to hundreds of backend daemons.

Users can use MySQL client tools to connect any frontend daemon to submit SQL 
query. Frontend receives the query and compiles it into query plans executable 
by the Backend. Then Frontend sends the query plan fragments to Backend. 
Backend will build a query execution DAG. Data is fetched and pipelined into 
the DAG. The final result response is sent to client via Frontend. The 
distribution of query fragment execution takes minimizing data movement and 
maximizing scan locality as the main goal.

== Background ==

At Baidu, Prior to Doris, different tools were deployed to solve diverse 
requirements in many ways. And when a use case requires the simultaneous 
availability of capabilities that cannot all be provided by a single tool, 
users were forced to build hybrid architectures that stitch multiple tools 
together, but we believe that they shouldn’t need to accept such inherent 
complexity. A storage system built to provide great performance across a broad 
range of workloads provides a more elegant solution to the problems that hybrid 
architectures aim to solve. Doris is the solution.

Doris is designed to be a simple and single tightly coupled system, not 
depending on other systems. Doris provides high concurrent low latency point 
query performance, but also provides high throughput queries of ad-hoc 
analysis. Doris provides bulk-batch data loading, but also provides near 
real-time mini-batch data loading. Doris also provides high availability, 
reliability, fault tolerance, and scalability.

== Rationale ==

Doris mainly integrates the technology of Google Mesa and Apache Impala.

Mesa is a highly scalable analytic data storage system that stores critical 
measurement data related to Google's Internet advertising business. Mesa is 
designed to satisfy complex and challenging set of users’ and systems’ 
requirements, including near real-time data ingestion and query ability, as 
well as high availability, reliability, fault tolerance, and scalability for 
large data and query volumes.

Impala is a modern, open-source MPP SQL engine architected from the ground up 
for the Hadoop data processing environment. At present, by virtue of its 
superior performance and rich functionality， Impala has been comparable to many 
commercial MPP database query engine. Mesa can satisfy the needs of many of our 
storage requirements, however Mesa itself does not provide a SQL query engine; 
Impala is a very good MPP SQL query engine, but the lack of a perfect 
distributed storage engine. So in the end we chose the combination of these two 
technologies.

Learning from Mesa’s data model, we developed a distributed storage engine. 
Unlike Mesa, this storage engine does not rely on any distributed file system. 
Then we deeply integrate this storage engine with Impala query engine. Query 
compiling, query execution coordination and catalog management of storage 
engine are integrated to be frontend daem

Re: [VOTE] Accept Doris into the Apache Incubator

[Sijie Guo]

+1 (non-binding)

It is a good project to incubate in the ASF. Doris (Palo) team was very
responsive to the questions raised in the discussion. I believe with the
help from Mentors, it can become a great project in the ASF.

- Sijie

On Thu, Jul 5, 2018 at 12:22 PM Dave Fisher  wrote:

> Hi All,
>
> I would like to start a VOTE to bring the Doris project as an Apache
> incubator podling.
>
> The ASF voting rules are described:
>
> https://www.apache.org/foundation/voting.html
>
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which
> only Incubator PMC member votes are binding.
>
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Doris into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Doris into the Apache Incubator because ...
>
> The proposal is listed below, but you can also access it on the wiki:
>
> https://wiki.apache.org/incubator/DorisProposal
>
> Best regards,
> Dave
>
> = Apache Doris =
>
> == Abstract ==
>
> Doris is a MPP-based interactive SQL data warehousing for reporting and
> analysis.
>
> == Proposal ==
>
> We propose to contribute the Doris codebase and associated artifacts (e.g.
> documentation, web-site content etc.) to the Apache Software Foundation,
> and aim to build an open community around Doris’s continued development in
> the ‘Apache Way’.
>
> === Overview of Doris ===
>
> Doris’s implementation consists of two daemons: Frontend (FE) and Backend
> (BE).
>
> **Frontend daemon** consists of query coordinator and catalog manager.
> Query coordinator is responsible for receiving users’ sql queries,
> compiling queries and managing queries execution. Catalog manager is
> responsible for managing metadata such as databases, tables, partitions,
> replicas and etc. Several frontend daemons could be deployed to guarantee
> fault-tolerance, and load balancing.
>
> **Backend daemon** stores the data and executes the query fragments. Many
> backend daemons could also be deployed to provide scalability and
> fault-tolerance.
>
> A typical Doris cluster generally composes of several frontend daemons and
> dozens to hundreds of backend daemons.
>
> Users can use MySQL client tools to connect any frontend daemon to submit
> SQL query. Frontend receives the query and compiles it into query plans
> executable by the Backend. Then Frontend sends the query plan fragments to
> Backend. Backend will build a query execution DAG. Data is fetched and
> pipelined into the DAG. The final result response is sent to client via
> Frontend. The distribution of query fragment execution takes minimizing
> data movement and maximizing scan locality as the main goal.
>
> == Background ==
>
> At Baidu, Prior to Doris, different tools were deployed to solve diverse
> requirements in many ways. And when a use case requires the simultaneous
> availability of capabilities that cannot all be provided by a single tool,
> users were forced to build hybrid architectures that stitch multiple tools
> together, but we believe that they shouldn’t need to accept such inherent
> complexity. A storage system built to provide great performance across a
> broad range of workloads provides a more elegant solution to the problems
> that hybrid architectures aim to solve. Doris is the solution.
>
> Doris is designed to be a simple and single tightly coupled system, not
> depending on other systems. Doris provides high concurrent low latency
> point query performance, but also provides high throughput queries of
> ad-hoc analysis. Doris provides bulk-batch data loading, but also provides
> near real-time mini-batch data loading. Doris also provides high
> availability, reliability, fault tolerance, and scalability.
>
> == Rationale ==
>
> Doris mainly integrates the technology of Google Mesa and Apache Impala.
>
> Mesa is a highly scalable analytic data storage system that stores
> critical measurement data related to Google's Internet advertising
> business. Mesa is designed to satisfy complex and challenging set of users’
> and systems’ requirements, including near real-time data ingestion and
> query ability, as well as high availability, reliability, fault tolerance,
> and scalability for large data and query volumes.
>
> Impala is a modern, open-source MPP SQL engine architected from the ground
> up for the Hadoop data processing environment. At present, by virtue of its
> superior performance and rich functionality， Impala has been comparable to
> many commercial MPP database query engine. Mesa can satisfy the needs of
> many of our storage requirements, however Mesa itself does not provide a
> SQL query engine; Impala is a very good MPP SQL query engine, but the lack
> of a perfect distributed storage engine. So in the end we chose the
> combination of these two technologies.
>
> Learning from Mesa’s data model, we developed a distributed storage
> engine. Unlike Mesa, this storage engine does not rely on any distributed
> file system. Then we deeply in

Re: [VOTE] Accept Doris into the Apache Incubator

[Dave Fisher]

Here is my +1 (binding)

> On Jul 5, 2018, at 12:22 PM, Dave Fisher  wrote:
> 
> Hi All,
> 
> I would like to start a VOTE to bring the Doris project as an Apache 
> incubator podling.
> 
> The ASF voting rules are described:
> 
> https://www.apache.org/foundation/voting.html 
> 
> 
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which only Incubator PMC member votes are binding.
> 
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Doris into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Doris into the Apache Incubator because ...
> 
> The proposal is listed below, but you can also access it on the wiki:
> 
> https://wiki.apache.org/incubator/DorisProposal 
> 
> 
> Best regards,
> Dave
> 
> = Apache Doris =
> 
> == Abstract ==
> 
> Doris is a MPP-based interactive SQL data warehousing for reporting and 
> analysis.
> 
> == Proposal ==
> 
> We propose to contribute the Doris codebase and associated artifacts (e.g. 
> documentation, web-site content etc.) to the Apache Software Foundation, and 
> aim to build an open community around Doris’s continued development in the 
> ‘Apache Way’.
> 
> === Overview of Doris ===
> 
> Doris’s implementation consists of two daemons: Frontend (FE) and Backend 
> (BE).
> 
> **Frontend daemon** consists of query coordinator and catalog manager. Query 
> coordinator is responsible for receiving users’ sql queries, compiling 
> queries and managing queries execution. Catalog manager is responsible for 
> managing metadata such as databases, tables, partitions, replicas and etc. 
> Several frontend daemons could be deployed to guarantee fault-tolerance, and 
> load balancing.
> 
> **Backend daemon** stores the data and executes the query fragments. Many 
> backend daemons could also be deployed to provide scalability and 
> fault-tolerance.
> 
> A typical Doris cluster generally composes of several frontend daemons and 
> dozens to hundreds of backend daemons.
> 
> Users can use MySQL client tools to connect any frontend daemon to submit SQL 
> query. Frontend receives the query and compiles it into query plans 
> executable by the Backend. Then Frontend sends the query plan fragments to 
> Backend. Backend will build a query execution DAG. Data is fetched and 
> pipelined into the DAG. The final result response is sent to client via 
> Frontend. The distribution of query fragment execution takes minimizing data 
> movement and maximizing scan locality as the main goal.
> 
> == Background ==
> 
> At Baidu, Prior to Doris, different tools were deployed to solve diverse 
> requirements in many ways. And when a use case requires the simultaneous 
> availability of capabilities that cannot all be provided by a single tool, 
> users were forced to build hybrid architectures that stitch multiple tools 
> together, but we believe that they shouldn’t need to accept such inherent 
> complexity. A storage system built to provide great performance across a 
> broad range of workloads provides a more elegant solution to the problems 
> that hybrid architectures aim to solve. Doris is the solution.
> 
> Doris is designed to be a simple and single tightly coupled system, not 
> depending on other systems. Doris provides high concurrent low latency point 
> query performance, but also provides high throughput queries of ad-hoc 
> analysis. Doris provides bulk-batch data loading, but also provides near 
> real-time mini-batch data loading. Doris also provides high availability, 
> reliability, fault tolerance, and scalability.
> 
> == Rationale ==
> 
> Doris mainly integrates the technology of Google Mesa and Apache Impala.
> 
> Mesa is a highly scalable analytic data storage system that stores critical 
> measurement data related to Google's Internet advertising business. Mesa is 
> designed to satisfy complex and challenging set of users’ and systems’ 
> requirements, including near real-time data ingestion and query ability, as 
> well as high availability, reliability, fault tolerance, and scalability for 
> large data and query volumes.
> 
> Impala is a modern, open-source MPP SQL engine architected from the ground up 
> for the Hadoop data processing environment. At present, by virtue of its 
> superior performance and rich functionality， Impala has been comparable to 
> many commercial MPP database query engine. Mesa can satisfy the needs of many 
> of our storage requirements, however Mesa itself does not provide a SQL query 
> engine; Impala is a very good MPP SQL query engine, but the lack of a perfect 
> distributed storage engine. So in the end we chose the combination of these 
> two technologies.
> 
> Learning from Mesa’s data model, we developed a distributed storage engine. 
> Unlike Mesa, this storage engine does not rely on any distributed file 
> system. Then we deeply integrate this storage engine with 

[VOTE] Accept Doris into the Apache Incubator

[Dave Fisher]

Hi All,

I would like to start a VOTE to bring the Doris project as an Apache incubator 
podling.

The ASF voting rules are described:

https://www.apache.org/foundation/voting.html 


A vote for accepting a new Apache Incubator podling is a majority vote for 
which only Incubator PMC member votes are binding.

This vote will run for at least 72 hours. Please VOTE as follows
[] +1 Accept Doris into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept Doris into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

https://wiki.apache.org/incubator/DorisProposal

Best regards,
Dave

= Apache Doris =

== Abstract ==

Doris is a MPP-based interactive SQL data warehousing for reporting and 
analysis.

== Proposal ==

We propose to contribute the Doris codebase and associated artifacts (e.g. 
documentation, web-site content etc.) to the Apache Software Foundation, and 
aim to build an open community around Doris’s continued development in the 
‘Apache Way’.

=== Overview of Doris ===

Doris’s implementation consists of two daemons: Frontend (FE) and Backend (BE).

**Frontend daemon** consists of query coordinator and catalog manager. Query 
coordinator is responsible for receiving users’ sql queries, compiling queries 
and managing queries execution. Catalog manager is responsible for managing 
metadata such as databases, tables, partitions, replicas and etc. Several 
frontend daemons could be deployed to guarantee fault-tolerance, and load 
balancing.

**Backend daemon** stores the data and executes the query fragments. Many 
backend daemons could also be deployed to provide scalability and 
fault-tolerance.

A typical Doris cluster generally composes of several frontend daemons and 
dozens to hundreds of backend daemons.

Users can use MySQL client tools to connect any frontend daemon to submit SQL 
query. Frontend receives the query and compiles it into query plans executable 
by the Backend. Then Frontend sends the query plan fragments to Backend. 
Backend will build a query execution DAG. Data is fetched and pipelined into 
the DAG. The final result response is sent to client via Frontend. The 
distribution of query fragment execution takes minimizing data movement and 
maximizing scan locality as the main goal.

== Background ==

At Baidu, Prior to Doris, different tools were deployed to solve diverse 
requirements in many ways. And when a use case requires the simultaneous 
availability of capabilities that cannot all be provided by a single tool, 
users were forced to build hybrid architectures that stitch multiple tools 
together, but we believe that they shouldn’t need to accept such inherent 
complexity. A storage system built to provide great performance across a broad 
range of workloads provides a more elegant solution to the problems that hybrid 
architectures aim to solve. Doris is the solution.

Doris is designed to be a simple and single tightly coupled system, not 
depending on other systems. Doris provides high concurrent low latency point 
query performance, but also provides high throughput queries of ad-hoc 
analysis. Doris provides bulk-batch data loading, but also provides near 
real-time mini-batch data loading. Doris also provides high availability, 
reliability, fault tolerance, and scalability.

== Rationale ==

Doris mainly integrates the technology of Google Mesa and Apache Impala.

Mesa is a highly scalable analytic data storage system that stores critical 
measurement data related to Google's Internet advertising business. Mesa is 
designed to satisfy complex and challenging set of users’ and systems’ 
requirements, including near real-time data ingestion and query ability, as 
well as high availability, reliability, fault tolerance, and scalability for 
large data and query volumes.

Impala is a modern, open-source MPP SQL engine architected from the ground up 
for the Hadoop data processing environment. At present, by virtue of its 
superior performance and rich functionality， Impala has been comparable to many 
commercial MPP database query engine. Mesa can satisfy the needs of many of our 
storage requirements, however Mesa itself does not provide a SQL query engine; 
Impala is a very good MPP SQL query engine, but the lack of a perfect 
distributed storage engine. So in the end we chose the combination of these two 
technologies.

Learning from Mesa’s data model, we developed a distributed storage engine. 
Unlike Mesa, this storage engine does not rely on any distributed file system. 
Then we deeply integrate this storage engine with Impala query engine. Query 
compiling, query execution coordination and catalog management of storage 
engine are integrated to be frontend daemon; query execution and data storage 
are integrated to be backend daemon. With this integration, we implemented a 
single, full-featured, high performance state the art of MPP database, as well 
as main