Re: Looking for Champion

[Li,De(BDG)]

Hi Tim, Todd,

Thank you for your response.

We are so sorry that we have not contribute any improvements to Impala so
far.
I think we will do that as soon, it is a good opportuniy to us to
participate
in open source community and learn to do things in Apache way.

One of causes is that We think most of our patches may not been accept by
Impala.
Because there is a big difference between Palo and Impala, our patch just
could
apply to Palo.

Firstly, as a query engine for Hadoop, Impala deeply depend on HDFS and
HBase 
(At least several years ago it was like this)
but Palo is just the opposite. We struggle to build a single tool which do
not 
depend on any other system.
The simplicity (of developing, deploying and using) and meeting many data
serving requirements in single system are the main feature of Palo.
So we just want a query engine from Impala rather than others such as
read/write Hive data.

Secondly, due to introduced Mesa data model. The Catalog is different from
Impala.
We developped a In-Memory Catalog and also support Rollup, aggregation
data 
model. As a consequnce, we have to change sql grammar based on Impala.

Thirdly, it is a big difference in Cluster manager and node deployment.
Contrast Impala, 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.

Now, as you mentioned, regarding Impala's goal is to be a full featured
data 
warehouse engine as well, maybe some of Palo's feature also usefull to
Impala. 
If it is possible, we are very happy to contribute code for Impala.
We are very appreciate for Impala community and we are looking forward to
corporate with Impala community in whatever way.

Best Regards,
Reed



在 2018/6/9 上午12:18， "Tim Armstrong"  写入:

>> Meanwhile we found Impala is a very good MPP SQL query engine, so we
>>integrated
>them together.
>
>Palo didn't integrate with Impala, it forked Impala's codebase and
>embedded
>it in its own repository. I don't remember any attempts from the Palo team
>to engage with the Impala community or attempt to work with us to
>contribute any improvements.
>
>It looks like Palo is still pulling in new code from Impala.  E.g. this
>commit includes a bunch of code I wrote as part of IMPALA-3200:
>https://github.com/baidu/palo/commit/2419384e8a211f10e7636afc6d3423700ba22
>b5a#diff-1c501d9a8b5c3d1d1cce48d5e1fb0edf
>
>The code isn't owned by any individual, I contributed it to Apache and
>it's
>free for anyone to do what they want to do with it, but pulling in
>improvements from other projects without any attempt to attribute it or
>contribute improvements back seems contrary to the Apache way.
>
>Anyway, maybe incubation is an opportunity for us to work together, but
>I'd
>hope that if Palo does go into incubation that it will rethink some of the
>practices it's been following.
>
>On Fri, Jun 8, 2018 at 9:12 AM, Todd Lipcon  wrote:
>
>> On Thu, Jun 7, 2018 at 11:55 PM, Li,De(BDG)  wrote:
>>
>> > Hi, Jim
>> >
>> > Thank you for your response.
>> > Actually, we start Palo in several years ago, and that time we
>>developed
>> > the storage engine based on Mesa technology.
>> > Meanwhile we found Impala is a very good MPP SQL query engine, so we
>> > integrated them together.
>> >
>>
>> From what I can tell of the Palo source, it's not so much an
>>integration as
>> a copied-and-modified codebase, right? i.e Palo does not use Impala as a
>> dependency, but rather shares a lot of code from the Impala project that
>> has since diverged.
>>
>>
>> >
>> > With this integration, the goal of Palo is to implement a single,
>> > full-featured, mysql protocol compatible data warehousing.
>> >
>>
>> That sounds pretty similar to the goals of the Impala project. Impala
>>isn't
>> MySQL-compatible at the moment but that seems more like a particular
>> feature that could be added rather than a distinct identity of the
>>project.
>> Otherwise, Impala's goal is to be a full featured data warehouse engine
>>as
>> well.
>>
>> Generally Apache has no rules against multiple projects fulfilling
>>similar
>> goals or use cases, even when those projects might compete. However I
>>think
>> it would be relatively unusual to incubate a project that appears to be
>> derived from a fork of an existing project, at least without first
>> considering whether the additional feature set could be contributed
>>back to
>> the existing community.
>>
>> -Todd
>>
>>
>> > 在 2018/6/8 下午1:55， "Jim Apple"  写入:
>> >

Re: Looking for Champion

[Li,De(BDG)]

Hi, Jim

Thank you for your response.
Actually, we start Palo in several years ago, and that time we developed
the storage engine based on Mesa technology.
Meanwhile we found Impala is a very good MPP SQL query engine, so we
integrated them together.

With this integration, the goal of Palo is to implement a single,
full-featured, mysql protocol compatible data warehousing.


Best regards,
Reed

在 2018/6/8 下午1:55， "Jim Apple"  写入:

>Hello! As a contributor to Impala, I’d be interested in hearing thoughts
>from the Palo community about integration between Impala and Palo.
>
>For instance, are there any apparent design goals of Impala that the Palo
>community thinks are fundamentally incompatible with Palo?
>
>Thanks,
>Jim
>
>On 2018/06/08 04:45:32, "Li,De(BDG)"  wrote:
>> Hi all,
>> 
>> I am Reed, as a developer worked with the team for Palo (a MPP-based
>>interactive SQL data warehousing).
>> https://github.com/baidu/palo/wiki/Palo-Overview
>> 
>> We propose to contribute Palo as an Apache Incubator project, and
>> we are still looking for possible Champion if anyone would like to
>>volunteer. Thanks a lot.
>> 
>> Best Regards,
>> Reed
>> 
>> ===
>> The draft of the proposal as below:
>> 
>> #Apache Palo
>> 
>> ##Abstract
>> 
>> Palo is a MPP-based interactive SQL data warehousing for reporting and
>>analysis.
>> 
>> ##Proposal
>> 
>> We propose to contribute the Palo codebase and associated artifacts
>>(e.g. documentation, web-site content etc.) to the Apache Software
>>Foundation with the intent of forming a productive, meritocratic and
>>open community around Palo’s continued development, according to the
>>‘Apache Way’.
>> 
>> Baidu owns several trademarks regarding Palo, and proposes to transfer
>>ownership of those trademarks in full to the ASF.
>> 
>> ###Overview of Palo
>> 
>> Palo’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 Palo 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 Palo, 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. Palo is
>>the solution.
>> 
>> Palo is designed to be a simple and single tightly coupled system, not
>>depending on other systems. Palo provides high concurrent low latency
>>point query performance, but also provides high throughput queries of
>>ad-hoc analysis. Palo provides bulk-batch data loading, but also
>>provides near real-time mini-batch data loading. Palo also provides high
>>availability, reliability, fault tolerance, and scalability.
>> 
>> ##Rationale
>> 
>> Palo 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
>>busine

Re: Looking for Champion

[Li,De(BDG)]

Hi Julian,

Thank you.

It looks like that we have to find another one.
If anyone has a good name, please feel free to let me know.

Best Regards,
Reed

在 2018/6/13 上午4:20， "Julian Hyde"  写入:

>Note that there is an existing database product called Palo - an open
>source OLAP engine by German company Jedox[1]. There there is a high
>likelihood that Palo would have to change its name during incubation, if
>accepted.
>
>Julian
>
>[1] https://en.wikipedia.org/wiki/Palo_(OLAP_database)
><https://en.wikipedia.org/wiki/Palo_(OLAP_database)>
>
>
>
>> On Jun 10, 2018, at 3:49 AM, Han Luke  wrote:
>> 
>> Cool Dave, it’s great to have you to be the campaign.
>> 
>> 
>> 
>> From: Tan,Zhongyi mailto:tanzhon...@baidu.com>>
>> Sent: Saturday, June 9, 2018 8:16:28 AM
>> To: general@incubator.apache.org <mailto:general@incubator.apache.org>
>> Subject: Re: Looking for Champion
>> 
>> thanks，willem
>> 
>> we are very appreciate.
>> 
>>> 在 2018年6月8日，23:03，Willem Jiang  写道：
>>> 
>>> Hi,
>>> 
>>> I'm willing to be the Mentor.
>>> Please count me in.
>>> 
>>> 
>>> 
>>> Willem Jiang
>>> 
>>> Twitter: willemjiang
>>> Weibo: 姜宁willem
>>> 
>>>> On Fri, Jun 8, 2018 at 8:59 PM, Dave Fisher 
>>>>wrote:
>>>> 
>>>> Hi -
>>>> 
>>>> I’m willing to Champion and Mentor. I have a couple of comments
>>>>inline.
>>>> I’ll look at dependency licenses later today. It’s early for me.
>>>> 
>>>> 
>>>>> On Jun 7, 2018, at 9:45 PM, Li,De(BDG)  wrote:
>>>>> 
>>>>> Hi all,
>>>>> 
>>>>> I am Reed, as a developer worked with the team for Palo (a MPP-based
>>>> interactive SQL data warehousing).
>>>>> https://github.com/baidu/palo/wiki/Palo-Overview
>>>>> 
>>>>> We propose to contribute Palo as an Apache Incubator project, and
>>>>> we are still looking for possible Champion if anyone would like to
>>>> volunteer. Thanks a lot.
>>>>> 
>>>>> Best Regards,
>>>>> Reed
>>>>> 
>>>>> ===
>>>>> The draft of the proposal as below:
>>>>> 
>>>>> #Apache Palo
>>>>> 
>>>>> ##Abstract
>>>>> 
>>>>> Palo is a MPP-based interactive SQL data warehousing for reporting
>>>>>and
>>>> analysis.
>>>>> 
>>>>> ##Proposal
>>>>> 
>>>>> We propose to contribute the Palo codebase and associated artifacts
>>>> (e.g. documentation, web-site content etc.) to the Apache Software
>>>> Foundation with the intent of forming a productive, meritocratic and
>>>>open
>>>> community around Palo’s continued development, according to the
>>>>‘Apache
>>>> Way’.
>>>>> 
>>>>> Baidu owns several trademarks regarding Palo, and proposes to
>>>>>transfer
>>>> ownership of those trademarks in full to the ASF.
>>>>> 
>>>>> ###Overview of Palo
>>>>> 
>>>>> Palo’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 Palo 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
>>

Re: Looking for Champion

[Li,De(BDG)]

Hi Dave,

Thank you very much your help and warmly welcome you as Palo’s Champion
and Mentor.
About licenses, we known as far as following:

--
1. aes/* mysql-5.6  GPL v2.1
2. util/mysql_dtoa.cpp Percona Server for MySQL GPL
3. http/mongoose.h mongoose MIT License
--


We will resolve the ASAP.



在 2018/6/8 下午8:59， "Dave Fisher"  写入:

>Hi -
>
>I’m willing to Champion and Mentor. I have a couple of comments inline.
>I’ll look at dependency licenses later today. It’s early for me.
>
>
>> On Jun 7, 2018, at 9:45 PM, Li,De(BDG)  wrote:
>> 
>> Hi all,
>> 
>> I am Reed, as a developer worked with the team for Palo (a MPP-based
>>interactive SQL data warehousing).
>> https://github.com/baidu/palo/wiki/Palo-Overview
>> 
>> We propose to contribute Palo as an Apache Incubator project, and
>> we are still looking for possible Champion if anyone would like to
>>volunteer. Thanks a lot.
>> 
>> Best Regards,
>> Reed
>> 
>> ===
>> The draft of the proposal as below:
>> 
>> #Apache Palo
>> 
>> ##Abstract
>> 
>> Palo is a MPP-based interactive SQL data warehousing for reporting and
>>analysis.
>> 
>> ##Proposal
>> 
>> We propose to contribute the Palo codebase and associated artifacts
>>(e.g. documentation, web-site content etc.) to the Apache Software
>>Foundation with the intent of forming a productive, meritocratic and
>>open community around Palo’s continued development, according to the
>>‘Apache Way’.
>> 
>> Baidu owns several trademarks regarding Palo, and proposes to transfer
>>ownership of those trademarks in full to the ASF.
>> 
>> ###Overview of Palo
>> 
>> Palo’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 Palo 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 Palo, 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. Palo is
>>the solution.
>> 
>> Palo is designed to be a simple and single tightly coupled system, not
>>depending on other systems. Palo provides high concurrent low latency
>>point query performance, but also provides high throughput queries of
>>ad-hoc analysis. Palo provides bulk-batch data loading, but also
>>provides near real-time mini-batch data loading. Palo also provides high
>>availability, reliability, fault tolerance, and scalability.
>> 
>> ##Rationale
>> 
>> Palo 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 tolera

Re: Looking for Champion

[Li,De(BDG)]

Thank you Willem, warmly welcome.

在 2018/6/8 下午11:03， "Willem Jiang"  写入:

>Hi,
>
>I'm willing to be the Mentor.
>Please count me in.
>
>
>
>Willem Jiang
>
>Twitter: willemjiang
>Weibo: 姜宁willem
>
>On Fri, Jun 8, 2018 at 8:59 PM, Dave Fisher  wrote:
>
>> Hi -
>>
>> I’m willing to Champion and Mentor. I have a couple of comments inline.
>> I’ll look at dependency licenses later today. It’s early for me.
>>
>>
>> > On Jun 7, 2018, at 9:45 PM, Li,De(BDG)  wrote:
>> >
>> > Hi all,
>> >
>> > I am Reed, as a developer worked with the team for Palo (a MPP-based
>> interactive SQL data warehousing).
>> > https://github.com/baidu/palo/wiki/Palo-Overview
>> >
>> > We propose to contribute Palo as an Apache Incubator project, and
>> > we are still looking for possible Champion if anyone would like to
>> volunteer. Thanks a lot.
>> >
>> > Best Regards,
>> > Reed
>> >
>> > ===
>> > The draft of the proposal as below:
>> >
>> > #Apache Palo
>> >
>> > ##Abstract
>> >
>> > Palo is a MPP-based interactive SQL data warehousing for reporting and
>> analysis.
>> >
>> > ##Proposal
>> >
>> > We propose to contribute the Palo codebase and associated artifacts
>> (e.g. documentation, web-site content etc.) to the Apache Software
>> Foundation with the intent of forming a productive, meritocratic and
>>open
>> community around Palo’s continued development, according to the ‘Apache
>> Way’.
>> >
>> > Baidu owns several trademarks regarding Palo, and proposes to transfer
>> ownership of those trademarks in full to the ASF.
>> >
>> > ###Overview of Palo
>> >
>> > Palo’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 Palo 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 Palo, 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. Palo is the solution.
>> >
>> > Palo is designed to be a simple and single tightly coupled system, not
>> depending on other systems. Palo provides high concurrent low latency
>>point
>> query performance, but also provides high throughput queries of ad-hoc
>> analysis. Palo provides bulk-batch data loading, but also provides near
>> real-time mini-batch data loading. Palo also provides high availability,
>> reliability, fault tolerance, and scalability.
>> >
>> > ##Rationale
>> >
>> > Palo mainly integrates the technology of Google Mesa and Apache
>>Impala.
>> >
>> > Mesa is a highly scalable analytic data storage system that stores
>

Re: Looking for Champion

[Li,De(BDG)]

Thanks to Jim's suggestion. We will seriously consider this proposal.
Also, for some of the opinions given by everyone,
the Palo development team will seriously discuss and then give
everyone a unified reply next week.



在 2018/6/9 上午7:41， "Jim Apple"  写入:

>>
>> Generally Apache has no rules against multiple projects fulfilling
>>similar
>> goals or use cases, even when those projects might compete. However I
>>think
>> it would be relatively unusual to incubate a project that appears to be
>> derived from a fork of an existing project, at least without first
>> considering whether the additional feature set could be contributed
>>back to
>> the existing community.
>>
>
>And this is something I'm really excited about. If only the storage system
>part of Palo were contributed to the ASF, and simultaneously the Palo
>community and the Impala community worked together to integrate the query
>engine work of Palo into Impala, then this could provide a lot of benefit
>to users, I think. My hope is that it would eliminate the toil the Palo
>community is engaged in by rebasing Impala changes (as Tim noticed).
>Impala, meanwhile, might benefit from some changes Palo has made, like
>SIMD
>filtering.
>
>This could be a lot of work, but the current system seems to already
>include quite a lot of inefficiency from the duplication.

Re: Looking for Champion

[Li,De(BDG)]

Regarding Licence's question, we will complete the repair as soon as possible 
before voting.

发件人: Dave Fisher mailto:dave2w...@comcast.net>>
答复: mailto:general@incubator.apache.org>>
日期: 2018年6月9日 星期六 上午2:10
至: mailto:general@incubator.apache.org>>
主题: Re: Looking for Champion

Yuck. That’s a mess. That is one very large diff.

I see a few files related to AES the were GPL converted to Apache which not 
allowed.
Copyrights were changed too which is also incorrect.

Changes to this file 
be/src/http/mongoose.h
 violate license and copyright of Sergey Lyubka

GitHub makes you expand each diff after awhile.

There are dependency licenses that might be issues too.

These licenses have not been evaluated by LEGAL.
* OpenLdap (OpenLDAP Software License)
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=blob;f=LICENSE;hb=e5f8117f0ce088d0bd7a8e18ddf37eaa40eb09b1
* rapidjson (Tencent)
Unknown
* cyrus-sasl (CMU License)
https://spdx.org/licenses/MIT-CMU.html
AKA MIT-CMU

Lots of work in evaluating licenses.

On Jun 8, 2018, at 9:46 AM, Ted Dunning 
mailto:ted.dunn...@gmail.com>> wrote:

Ouch.

The copyright in question was attached to code from the source code for
mySQL. There is no way that code can be in an Apache project.

Given the cut and paste history, it seems like it will require a very
detailed audit of code history or web searches to find where the original
code came from. The my_aes.c and .h files, for instance, have no hint in
their history that they came from GPL'ed code.

Yeah. Lot’s of oversight.

If we accept this proposal we need a Mentor who has time to help with this mess.

I don’t know that I have the time to lead that effort. Anyone?

Regards,
Dave


On Fri, Jun 8, 2018 at 5:37 PM Todd Lipcon 
mailto:t...@cloudera.com>> wrote:

...

+1. Also briefly browsing the code I found suspicious commits like this
one:

https://github.com/baidu/palo/commit/6486be64c319fe0beb8c6b4430c1662de54f182e

... in which a GPL license copyright by Oracle was "fixed" to be an Apache
license copyright Baidu.

So if this project does enter incubation I think we should be extra careful
to audit the origins of all of the source code.

Re: Looking for Champion

[Li,De(BDG)]

Hi Todd,

Thank you for your response.

It is serious mistake to replace Oracle license to Apache when updating
license with a script.

We have not check carefully, actually, those file no longer been used.
So I removed them and made a new commit.

https://github.com/baidu/palo/commit/ac770c33d445a4c18a0b74f56b28a4180b30bf
b7

Best Regards,
Reed


在 2018/6/9 上午12:37， "Todd Lipcon"  写入:

>On Fri, Jun 8, 2018 at 9:18 AM, Tim Armstrong 
>wrote:
>
>> > Meanwhile we found Impala is a very good MPP SQL query engine, so we
>> integrated
>> them together.
>>
>> Palo didn't integrate with Impala, it forked Impala's codebase and
>>embedded
>> it in its own repository. I don't remember any attempts from the Palo
>>team
>> to engage with the Impala community or attempt to work with us to
>> contribute any improvements.
>>
>> It looks like Palo is still pulling in new code from Impala.  E.g. this
>> commit includes a bunch of code I wrote as part of IMPALA-3200:
>> https://github.com/baidu/palo/commit/2419384e8a211f10e7636afc6d3423
>> 700ba22b5a#diff-1c501d9a8b5c3d1d1cce48d5e1fb0edf
>>
>> The code isn't owned by any individual, I contributed it to Apache and
>>it's
>> free for anyone to do what they want to do with it, but pulling in
>> improvements from other projects without any attempt to attribute it or
>> contribute improvements back seems contrary to the Apache way.
>>
>
>+1. Also briefly browsing the code I found suspicious commits like this
>one:
>https://github.com/baidu/palo/commit/6486be64c319fe0beb8c6b4430c1662de54f1
>82e
>
>... in which a GPL license copyright by Oracle was "fixed" to be an Apache
>license copyright Baidu.
>
>So if this project does enter incubation I think we should be extra
>careful
>to audit the origins of all of the source code.
>
>-Todd
>
>
>> On Fri, Jun 8, 2018 at 9:12 AM, Todd Lipcon  wrote:
>>
>> > On Thu, Jun 7, 2018 at 11:55 PM, Li,De(BDG)  wrote:
>> >
>> > > Hi, Jim
>> > >
>> > > Thank you for your response.
>> > > Actually, we start Palo in several years ago, and that time we
>> developed
>> > > the storage engine based on Mesa technology.
>> > > Meanwhile we found Impala is a very good MPP SQL query engine, so we
>> > > integrated them together.
>> > >
>> >
>> > From what I can tell of the Palo source, it's not so much an
>>integration
>> as
>> > a copied-and-modified codebase, right? i.e Palo does not use Impala
>>as a
>> > dependency, but rather shares a lot of code from the Impala project
>>that
>> > has since diverged.
>> >
>> >
>> > >
>> > > With this integration, the goal of Palo is to implement a single,
>> > > full-featured, mysql protocol compatible data warehousing.
>> > >
>> >
>> > That sounds pretty similar to the goals of the Impala project. Impala
>> isn't
>> > MySQL-compatible at the moment but that seems more like a particular
>> > feature that could be added rather than a distinct identity of the
>> project.
>> > Otherwise, Impala's goal is to be a full featured data warehouse
>>engine
>> as
>> > well.
>> >
>> > Generally Apache has no rules against multiple projects fulfilling
>> similar
>> > goals or use cases, even when those projects might compete. However I
>> think
>> > it would be relatively unusual to incubate a project that appears to
>>be
>> > derived from a fork of an existing project, at least without first
>> > considering whether the additional feature set could be contributed
>>back
>> to
>> > the existing community.
>> >
>> > -Todd
>> >
>> >
>> > > 在 2018/6/8 下午1:55， "Jim Apple"  写入:
>> > >
>> > > >Hello! As a contributor to Impala, I’d be interested in hearing
>> thoughts
>> > > >from the Palo community about integration between Impala and Palo.
>> > > >
>> > > >For instance, are there any apparent design goals of Impala that
>>the
>> > Palo
>> > > >community thinks are fundamentally incompatible with Palo?
>> > > >
>> > > >Thanks,
>> > > >Jim
>> > > >
>> > > >On 2018/06/08 04:45:32, "Li,De(BDG)"  wrote:
>> > > >> Hi all,
>> > > >>
>> > > >> I am Reed, as a developer worked with the team for Palo 

Re: Looking for Champion

[Li,De(BDG)]

Hi all,

About Palo, we have fixed following issues.

1. Related Impala
For issues mentioned by Jim, Todd and Tim, I have replied on last Saturday.

2、Lisence issue
For issues mentioned by Todd and Ted.
1) be/aes/* come from mysql-5.6, GPL v2.1 license
Fixed: removed aes related codes.
https://github.com/baidu/palo/commit/ac770c33d445a4c18a0b74f56b28a4180b30bf
b7
https://github.com/baidu/palo/commit/3c9f2ae6695ffebe41e39b6bf6544077698f1c
ed

2) be/util/mysql_dtoa.cpp copy from MySQL, GPL license
Fixed: removed mysql_dtoa related codes.
https://github.com/baidu/palo/commit/bfe1bc7cf39e165a7c52b2c941550975b1f841
a1

3) be/http/mongoose.h, Copyright (c) 2004-2012 Sergey Lyubka
Fixed: restored to original lisence, we are searching another http server
to replace it.
https://github.com/baidu/palo/commit/81baef34f48a2dbe7401712c5e0a50f59f04a8
31

4) be/rpc/*
Fixed: We have replaced it with brpc, and we will remove Hypertable after
few weeks for waiting users' upgrade to brpc.
https://github.com/baidu/palo/tree/master/be/src/rpc

3、Dependency licenses
For issue mentioned by Dave, It looks like that Palo have not depend on
OpenLdap and cyrus-sasl directly,
but some thirdpary libraries need them to compile, libcurl and gperftools
for instance.
For rapidjson, we are looking for alternative one.

4、About the name of Palo
For issue mentioned by Julian.
We are figuring out a better one.

Best Regards,
Reed



在 2018/6/13 上午8:54， "Li,De(BDG)"  写入:

>Hi Julian,
>
>Thank you.
>
>It looks like that we have to find another one.
>If anyone has a good name, please feel free to let me know.
>
>Best Regards,
>Reed
>
>在 2018/6/13 上午4:20， "Julian Hyde"  写入:
>
>>Note that there is an existing database product called Palo - an open
>>source OLAP engine by German company Jedox[1]. There there is a high
>>likelihood that Palo would have to change its name during incubation, if
>>accepted.
>>
>>Julian
>>
>>[1] https://en.wikipedia.org/wiki/Palo_(OLAP_database)
>><https://en.wikipedia.org/wiki/Palo_(OLAP_database)>
>>
>>
>>
>>> On Jun 10, 2018, at 3:49 AM, Han Luke  wrote:
>>> 
>>> Cool Dave, it’s great to have you to be the campaign.
>>> 
>>> 
>>> 
>>> From: Tan,Zhongyi mailto:tanzhon...@baidu.com>>
>>> Sent: Saturday, June 9, 2018 8:16:28 AM
>>> To: general@incubator.apache.org <mailto:general@incubator.apache.org>
>>> Subject: Re: Looking for Champion
>>> 
>>> thanks，willem
>>> 
>>> we are very appreciate.
>>> 
>>>> 在 2018年6月8日，23:03，Willem Jiang  写道：
>>>> 
>>>> Hi,
>>>> 
>>>> I'm willing to be the Mentor.
>>>> Please count me in.
>>>> 
>>>> 
>>>> 
>>>> Willem Jiang
>>>> 
>>>> Twitter: willemjiang
>>>> Weibo: 姜宁willem
>>>> 
>>>>> On Fri, Jun 8, 2018 at 8:59 PM, Dave Fisher 
>>>>>wrote:
>>>>> 
>>>>> Hi -
>>>>> 
>>>>> I’m willing to Champion and Mentor. I have a couple of comments
>>>>>inline.
>>>>> I’ll look at dependency licenses later today. It’s early for me.
>>>>> 
>>>>> 
>>>>>> On Jun 7, 2018, at 9:45 PM, Li,De(BDG)  wrote:
>>>>>> 
>>>>>> Hi all,
>>>>>> 
>>>>>> I am Reed, as a developer worked with the team for Palo (a MPP-based
>>>>> interactive SQL data warehousing).
>>>>>> https://github.com/baidu/palo/wiki/Palo-Overview
>>>>>> 
>>>>>> We propose to contribute Palo as an Apache Incubator project, and
>>>>>> we are still looking for possible Champion if anyone would like to
>>>>> volunteer. Thanks a lot.
>>>>>> 
>>>>>> Best Regards,
>>>>>> Reed
>>>>>> 
>>>>>> ===
>>>>>> The draft of the proposal as below:
>>>>>> 
>>>>>> #Apache Palo
>>>>>> 
>>>>>> ##Abstract
>>>>>> 
>>>>>> Palo is a MPP-based interactive SQL data warehousing for reporting
>>>>>>and
>>>>> analysis.
>>>>>> 
>>>>>> ##Proposal
>>>>>> 
>>>>>> We propose to contribute the Palo codebase and associated artifacts
>>>>> (e.g. documentation, web-site content etc.) to the Apache Software
>>>>> Foundatio

Re: Looking for Champion

[Li,De(BDG)]

   Copyrights were changed too which is also incorrect.

Yes, we know that, I have fixed this mistake as following.
https://github.com/baidu/palo/commit/ac770c33d445a4c18a0b74f56b28a4180b30bf
b7

As you mentioned, we will recheck and make sure if Open LDAP is necessary
for Palo. 

Best Regards,
Reed


在 2018/6/9 上午4:13， "Ted Dunning"  写入:

>Open LDAP is a form of copy-left. It requires source code distribution of
>binary packaged versions.
>
>
>
>On Fri, Jun 8, 2018 at 7:10 PM Dave Fisher  wrote:
>
>> Yuck. That’s a mess. That is one very large diff.
>>
>> I see a few files related to AES the were GPL converted to Apache which
>> not allowed.
>> Copyrights were changed too which is also incorrect.
>>
>> Changes to this file be/src/http/mongoose.h
>> 
>>>f182e#diff-586168bd25cfbf3bc8bc1b52abc4206c> violate
>> license and copyright of Sergey Lyubka
>>
>> GitHub makes you expand each diff after awhile.
>>
>> There are dependency licenses that might be issues too.
>>
>> These licenses have not been evaluated by LEGAL.
>> * OpenLdap (OpenLDAP Software License)
>>
>> 
>>http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=blob;f=LICENSE;
>>hb=e5f8117f0ce088d0bd7a8e18ddf37eaa40eb09b1
>> * rapidjson (Tencent)
>> Unknown
>> * cyrus-sasl (CMU License)
>> https://spdx.org/licenses/MIT-CMU.html
>> AKA MIT-CMU
>>
>> Lots of work in evaluating licenses.
>>
>> On Jun 8, 2018, at 9:46 AM, Ted Dunning  wrote:
>>
>> Ouch.
>>
>> The copyright in question was attached to code from the source code for
>> mySQL. There is no way that code can be in an Apache project.
>>
>> Given the cut and paste history, it seems like it will require a very
>> detailed audit of code history or web searches to find where the
>>original
>> code came from. The my_aes.c and .h files, for instance, have no hint in
>> their history that they came from GPL'ed code.
>>
>>
>> Yeah. Lot’s of oversight.
>>
>> If we accept this proposal we need a Mentor who has time to help with
>>this
>> mess.
>>
>> I don’t know that I have the time to lead that effort. Anyone?
>>
>> Regards,
>> Dave
>>
>>
>> On Fri, Jun 8, 2018 at 5:37 PM Todd Lipcon  wrote:
>>
>> ...
>>
>> +1. Also briefly browsing the code I found suspicious commits like this
>> one:
>>
>>
>> 
>>https://github.com/baidu/palo/commit/6486be64c319fe0beb8c6b4430c1662de54f
>>182e
>>
>> ... in which a GPL license copyright by Oracle was "fixed" to be an
>>Apache
>> license copyright Baidu.
>>
>> So if this project does enter incubation I think we should be extra
>>careful
>> to audit the origins of all of the source code.
>>
>>
>>
>>

Re: Looking for Champion

[Li,De(BDG)]

Hi Dave,

Thank you for your response.

As you mentioned that mongoose.h, it is serious mistake to replace license when 
updating Apache
license with a automatic script.

I have fixed it as following:
https://github.com/baidu/palo/commit/611afcd125dc136c58d7feb5552c26e9b215878a

By the way, I wonder Palo just use OpenLdap with binary way, is it still have 
license issue?

Best Regards,
Reed

发件人: Dave Fisher mailto:dave2w...@comcast.net>>
答复: mailto:general@incubator.apache.org>>
日期: 2018年6月9日 星期六 上午2:10
至: mailto:general@incubator.apache.org>>
主题: Re: Looking for Champion

Yuck. That’s a mess. That is one very large diff.

I see a few files related to AES the were GPL converted to Apache which not 
allowed.
Copyrights were changed too which is also incorrect.

Changes to this file 
be/src/http/mongoose.h
 violate license and copyright of Sergey Lyubka

GitHub makes you expand each diff after awhile.

There are dependency licenses that might be issues too.

These licenses have not been evaluated by LEGAL.
* OpenLdap (OpenLDAP Software License)
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=blob;f=LICENSE;hb=e5f8117f0ce088d0bd7a8e18ddf37eaa40eb09b1
* rapidjson (Tencent)
Unknown
* cyrus-sasl (CMU License)
https://spdx.org/licenses/MIT-CMU.html
AKA MIT-CMU

Lots of work in evaluating licenses.

On Jun 8, 2018, at 9:46 AM, Ted Dunning 
mailto:ted.dunn...@gmail.com>> wrote:

Ouch.

The copyright in question was attached to code from the source code for
mySQL. There is no way that code can be in an Apache project.

Given the cut and paste history, it seems like it will require a very
detailed audit of code history or web searches to find where the original
code came from. The my_aes.c and .h files, for instance, have no hint in
their history that they came from GPL'ed code.

Yeah. Lot’s of oversight.

If we accept this proposal we need a Mentor who has time to help with this mess.

I don’t know that I have the time to lead that effort. Anyone?

Regards,
Dave


On Fri, Jun 8, 2018 at 5:37 PM Todd Lipcon 
mailto:t...@cloudera.com>> wrote:

...

+1. Also briefly browsing the code I found suspicious commits like this
one:

https://github.com/baidu/palo/commit/6486be64c319fe0beb8c6b4430c1662de54f182e

... in which a GPL license copyright by Oracle was "fixed" to be an Apache
license copyright Baidu.

So if this project does enter incubation I think we should be extra careful
to audit the origins of all of the source code.

Looking for Champion

[Li,De(BDG)]

Hi all,

I am Reed, as a developer worked with the team for Palo (a MPP-based 
interactive SQL data warehousing).
https://github.com/baidu/palo/wiki/Palo-Overview

We propose to contribute Palo as an Apache Incubator project, and
we are still looking for possible Champion if anyone would like to volunteer. 
Thanks a lot.

Best Regards,
Reed

===
The draft of the proposal as below:

#Apache Palo

##Abstract

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

##Proposal

We propose to contribute the Palo codebase and associated artifacts (e.g. 
documentation, web-site content etc.) to the Apache Software Foundation with 
the intent of forming a productive, meritocratic and open community around 
Palo’s continued development, according to the ‘Apache Way’.

Baidu owns several trademarks regarding Palo, and proposes to transfer 
ownership of those trademarks in full to the ASF.

###Overview of Palo

Palo’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 Palo 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 Palo, 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. Palo is the solution.

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

##Rationale

Palo 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 maintaining the simplicity.

##Current Status

Palo has been an open source project on GitHub (https://github.com/baidu/palo).

###Meritocracy

Palo has been 

Re: [ANN] Please welcome Justin Mclean as the new Incubator PMC chair!

[Li,De(BDG)]

Congratulations Justin!


-- Reed

在 2018/6/6 上午3:40， "Dave Fisher"  写入:

>Thank you very much John!
>
>Congratulations Justin!
>
>> On Jun 4, 2018, at 3:12 AM, Bertrand Delacretaz
>> wrote:
>> 
>> Hi,
>> 
>> John D. Ament recently announced his desire to step down from the
>> Incubator PMC chair role. Thank you so much John for your efficient
>> service here, "retiring" from that is certainly well deserved!
>> 
>> The Incubator PMC had the difficult task of choosing between a handful
>> of excellent candidates and has selected Justin as our new chair. The
>> ASF's Board of Directors has ratified this choice at our May meeting.
>> 
>> Please join me in welcoming Jusin as our new PMC chair! Justin's been
>> very active in the Incubator in the last few years, it's great to see
>> him step up to this role.
>> 
>> -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: Looking for Champion

[Li,De(BDG)]

Hi Jim,

Do you have any questions or suggestions about this Roadmap, please feel
free to let us know.

Best Regards,
Reed 

On 2018/6/21 下午8:06， "Li,De(BDG)"  wrote:

>We have a general Plan or Roadmap:
>
>1. Find out the code, modules, components which duplicates of Impala;
>2. Determine the features which could be merged to Impala under Impala
>community support.
>3, Define clearly the interface between the query engine and other
>components, such as the storage engine, metadata management, mysql server,
>load and export modules, web server and so on.
>4. Separate the Impala query engine from Palo.
>
>
>Best Regards,
>Reed
>
>On 2018/6/19 下午9:48， "Jim Apple"  wrote:
>
>>>
>>> I'm not sure if Palo is just a storage system but definitely we will
>>> separate query engine from Palo.
>>>
>>
>>That's great news, and I think it will benefit users of Impala and Palo.
>>
>>
>>> Of cource, as you mentioned, "this could be a lot of work", so it will
>>> take a long time and we also hope that Impala community could support
>>>us.
>>>
>>
>>Yes, I expect so.
>
>?B婯
>KKKCB??[溳
>X溫軞X橩??K[XZ[??賉橽榌?][溳X溫軞X橮?[樰X榏?軏榎?X?K涇櫭B憶軋?Y??]?[蹣[??
圹[X[???K[XZ[??賉橽榌
>?Z?[???[樰X榏?軏榎?X?K涇櫭B

Re: [DISCUSS] Doris Proposal

[Li,De(BDG)]

Hi Dave,

Well done, thanks a lot.

Best Regards,
Reed


On 2018/6/30 上午7:27， "Dave Fisher"  wrote:

>Hi -
>
>The Doris Proposal is available at
>https://wiki.apache.org/incubator/DorisProposal
>
>It was updated to reflect the discussions that occurred under the thread
>https://lists.apache.org/thread.html/74a3f3f945403b50515c658047d3284955288
>a637207e4f97ecc15d1@%3Cgeneral.incubator.apache.org%3E
>
>Please provide any necessary updates.
>
>We would like to start the VOTE on Monday.
>
>Regards,
>Dave

Re: Looking for Champion

[Li,De(BDG)]

 load should not be very large.

##Initial Committers

* Ruyue Ma (https://github.com/maruyue, maru...@baidu.com)
* Chun Zhao (https://github.com/imay, buaa.zh...@gmail.com)
* Mingyu Chen (https://github.com/morningman,chenmin...@baidu.com)
* De Li（https://github.com/lide-reed, mailtol...@sina.com）
* Hao Chen (https://github.com/chenhao7253886, chenha...@baidu.com)
* Chaoyong Li (https://github.com/cyongli, lichaoy...@baidu.com)
* Bin Lin (https://github.com/lingbin, lingbi...@gmail.com)
* Sijie Guo (guosi...@gmail.com)
* Zheng Shao (zs...@apache.org)

##Affiliations

The initial committers are employees of Baidu Inc..

##Sponsors

###Champion

Dave Fisher, dave2w...@comcast.net

###Nominated Mentors

* Luke Han, luke...@apache.org
* Dave Fisher, dave2w...@comcast.net
* Willem Jiang, willem.ji...@gmail.com

###Sponsoring Entity

We are requesting the Incubator to sponsor this project.

On 2018/6/19 下午6:54， "Li,De(BDG)" mailto:l...@baidu.com>> wrote:

Hi Dave,

Thank you for your summary.

For #1, I got it, we will find a new name ASAP within several days.

For #2, I see, about license, we are rechecking all licenses of components in 
Palo, and we have fixed most of those we found as I wrote in last email. Next, 
we will continue to do this work carefully.

For #3, We have reflected upon Jim's suggestion, and we will try to find out or 
define a cleanly interface between Palo and Impala and to determine which parts 
should keep in Palo and which parts should as patches for Impala. More detail 
and roadmap are still to be work out.

For #4, I accepted your suggestion and I will update proposal.

Once I have a new name, I will send you with updated proposal.

Best Regards,
Reed

发件人: Dave Fisher mailto:dave2w...@comcast.net>>
答复: mailto:general@incubator.apache.org>>
日期: 2018年6月19日 星期二 上午2:08
至: mailto:general@incubator.apache.org>>
主题: Re: Looking for Champion

Hi Li,De -

Since I agreed to champion this project I think that we need a summary about 
what the Incubator PMC cares about in order to accept a podling. What the 
prospective project needs to address. We also need to be clear what should 
happen during Incubation and at what time. I think that many of the questions 
that came up in this thread had to do with assessing how much effort it will 
take to Incubate Palo (or whatever the name will be)

(1) The name Palo. Since there seems to be an issue with that name we should 
have a new name. It is not unknown for a podling to change its name, but that 
does generate extra work for Infrastructure to change the name after podling 
start up. It would be our preference for Palo to find a new name prior to 
VOTING on the proposal. Please do this elsewhere and come back to me with the 
new name so that I can help with the updated proposal.

(2) Licensing of the software. Several bits came up as questionable. Regardless 
of cleanup that has already occurred we have identified that we will need to be 
very careful. It will be important to discuss and carefully handle the Software 
Grant Agreement to make sure that the source listed is correct. I think that 
the SGA must come early during incubation.

(3) Relationship with Impala. Palo has apparently forked portions of Impala. 
This means that some are concerned that there is a missed synergy with the 
Apache Impala project. Is there a clean interface that can be built between the 
projects? It would help if the Palo developers would explore this with Impala 
at d...@impala.apache.org<mailto:d...@impala.apache.org>.

That said, part of the Incubation process is to learn the Apache Way. IMHO it 
is ok for the relationship between Impala PMC and a pooling PPMC to be a work 
in process.

(4) Currently, Willem, Luke Han and Dave Fisher are qualified to officially 
mentor. I suggest that Sijie Guo and Zheng Shao be included as Initial 
Committers in order to help from within the PPMC.

On Jun 14, 2018, at 11:03 AM, Jim Apple 
mailto:jbap...@cloudera.com.INVALID>> wrote:

I don't want to be a stickler, but I don't think "For issues mentioned by
Jim, Todd and Tim, I have replied on last Saturday."

To my email about Palo being an ASF project as a storage system without a
query engine, you replied only, "We will seriously consider this proposal."

I see no response to Tim's concern that "The code isn't owned by any
individual, I contributed it to Apache and it's
free for anyone to do what they want to do with it, but pulling in
improvements from other projects without any attempt to attribute it or
contribute improvements back seems contrary to the Apache way.”

Jim - do you need answers to these concerns prior to agreeing to accept this 
project into the Incubator?

Regards,
Dave


On Thu, Jun 14, 2018 at 12:48 AM, Li,De(BDG) 
mailto:l...@baidu.com>> wrote:

Hi all,

About Palo, we have fixed following issues.

1. Related Impala
For issues mentioned by Jim, Todd and Tim, I have replied on la

Re: Looking for Champion

[Li,De(BDG)]

We have a general Plan or Roadmap:

1. Find out the code, modules, components which duplicates of Impala;
2. Determine the features which could be merged to Impala under Impala
community support.
3, Define clearly the interface between the query engine and other
components, such as the storage engine, metadata management, mysql server,
load and export modules, web server and so on.
4. Separate the Impala query engine from Palo.


Best Regards,
Reed

On 2018/6/19 下午9:48， "Jim Apple"  wrote:

>>
>> I'm not sure if Palo is just a storage system but definitely we will
>> separate query engine from Palo.
>>
>
>That's great news, and I think it will benefit users of Impala and Palo.
>
>
>> Of cource, as you mentioned, "this could be a lot of work", so it will
>> take a long time and we also hope that Impala community could support
>>us.
>>
>
>Yes, I expect so.

Re: Looking for Champion

[Li,De(BDG)]

Hi Jim,

Thank you for your response.

We have reflected upon your suggestion and we agree with you for the most
part.
We will try to find out or define a cleanly interface between Palo and
Impala and to determine which parts should keep in Palo and which parts
should as patches for Impala.
I'm not sure if Palo is just a storage system but definitely we will
separate query engine from Palo.
Of cource, as you mentioned, "this could be a lot of work", so it will
take a long time and we also hope that Impala community could support us.

For Tim's concern, as I said in another email, what we have done ever
maybe not in Apache way but I think it is a good opportuniy to us to
participate in open source community and learn to do things in Apache way,
including how to corporate with Impala community (indeed we lack of
interaction).

Best Regards,
Reed



在 2018/6/15 上午2:03， "Jim Apple"  写入:

>I don't want to be a stickler, but I don't think "For issues mentioned by
>Jim, Todd and Tim, I have replied on last Saturday."
>
>To my email about Palo being an ASF project as a storage system without a
>query engine, you replied only, "We will seriously consider this
>proposal."
>
>I see no response to Tim's concern that "The code isn't owned by any
>individual, I contributed it to Apache and it's
>free for anyone to do what they want to do with it, but pulling in
>improvements from other projects without any attempt to attribute it or
>contribute improvements back seems contrary to the Apache way."
>
>On Thu, Jun 14, 2018 at 12:48 AM, Li,De(BDG)  wrote:
>
>> Hi all,
>>
>> About Palo, we have fixed following issues.
>>
>> 1. Related Impala
>> For issues mentioned by Jim, Todd and Tim, I have replied on last
>>Saturday.
>>
>> 2、Lisence issue
>> For issues mentioned by Todd and Ted.
>> 1) be/aes/* come from mysql-5.6, GPL v2.1 license
>> Fixed: removed aes related codes.
>> https://github.com/baidu/palo/commit/ac770c33d445a4c18a0b74f56b28a4
>> 180b30bf
>> b7
>> https://github.com/baidu/palo/commit/3c9f2ae6695ffebe41e39b6bf65440
>> 77698f1c
>> ed
>>
>> 2) be/util/mysql_dtoa.cpp copy from MySQL, GPL license
>> Fixed: removed mysql_dtoa related codes.
>> https://github.com/baidu/palo/commit/bfe1bc7cf39e165a7c52b2c9415509
>> 75b1f841
>> a1
>>
>> 3) be/http/mongoose.h, Copyright (c) 2004-2012 Sergey Lyubka
>> Fixed: restored to original lisence, we are searching another http
>>server
>> to replace it.
>> https://github.com/baidu/palo/commit/81baef34f48a2dbe7401712c5e0a50
>> f59f04a8
>> 31
>>
>> 4) be/rpc/*
>> Fixed: We have replaced it with brpc, and we will remove Hypertable
>>after
>> few weeks for waiting users' upgrade to brpc.
>> https://github.com/baidu/palo/tree/master/be/src/rpc
>>
>> 3、Dependency licenses
>> For issue mentioned by Dave, It looks like that Palo have not depend on
>> OpenLdap and cyrus-sasl directly,
>> but some thirdpary libraries need them to compile, libcurl and
>>gperftools
>> for instance.
>> For rapidjson, we are looking for alternative one.
>>
>> 4、About the name of Palo
>> For issue mentioned by Julian.
>> We are figuring out a better one.
>>
>> Best Regards,
>> Reed
>>
>>
>>
>> 在 2018/6/13 上午8:54， "Li,De(BDG)"  写入:
>>
>> >Hi Julian,
>> >
>> >Thank you.
>> >
>> >It looks like that we have to find another one.
>> >If anyone has a good name, please feel free to let me know.
>> >
>> >Best Regards,
>> >Reed
>> >
>> >在 2018/6/13 上午4:20， "Julian Hyde"  写入:
>> >
>> >>Note that there is an existing database product called Palo - an open
>> >>source OLAP engine by German company Jedox[1]. There there is a high
>> >>likelihood that Palo would have to change its name during incubation,
>>if
>> >>accepted.
>> >>
>> >>Julian
>> >>
>> >>[1] https://en.wikipedia.org/wiki/Palo_(OLAP_database)
>> >><https://en.wikipedia.org/wiki/Palo_(OLAP_database)>
>> >>
>> >>
>> >>
>> >>> On Jun 10, 2018, at 3:49 AM, Han Luke  wrote:
>> >>>
>> >>> Cool Dave, it’s great to have you to be the campaign.
>> >>>
>> >>>
>> >>> 
>> >>> From: Tan,Zhongyi ><mailto:tanzhon...@baidu.com>>
>> >>> Sent: Saturday, June 9, 2018 8:16:28 AM
>> >>> 

Re: Looking for Champion

[Li,De(BDG)]

Hi Ryan,

Thank you for your response.

For #1, I admit we have not build open and inclusive community so far yet,
but we have realized the importance.
So one of our aims to proposal to enter incubrator is that to build a
well-cooperated community and worked with others in Apache way.


For #2, It is not only "catching all the obvious one”, actually, we
scanned and rechecked all code carefully and worked out a todo list.
Now we are working on it and fixed one by one.

Best Regards,
Reed

在 2018/6/19 上午3:07， "Ryan Blue"  写入:

>I agree with Jim, at least mostly.
>
>I don't mind code and toil duplication between projects in itself, but I
>think that the current state of the project shows that there are two large
>risks to the potential Palo podling (for lack of a better name):
>
>1. The choice not to work with the Impala community initially shows a risk
>of not working with others when it may be more difficult to do so than
>not.
>I think this should be directly addressed in the proposal: how do we know
>that this will be an open and inclusive community willing to work with
>others with slightly different goals?
>2. The license problems so far show that the project has not paid adequate
>attention to licensing up to now, which is a big risk. I'd like to see
>what
>kind of licensing scrub is proposed before the potential podling's first
>release. I don't think that catching all the obvious ones is sufficient.
>
>rb
>
>On Mon, Jun 18, 2018 at 11:51 AM, Jim Apple 
>wrote:
>
>> I'm not a binding vote on incubator entry, but I think it would be
>> great to have roadmaps as soon as feasible on addressing Tim's concern
>> (which is deeply related to #2, "Licensing") and on addressing the
>> code and toil duplication.
>>
>> On Mon, Jun 18, 2018 at 11:08 AM, Dave Fisher 
>> wrote:
>> > Hi Li,De -
>> >
>> > Since I agreed to champion this project I think that we need a summary
>> about
>> > what the Incubator PMC cares about in order to accept a podling. What
>>the
>> > prospective project needs to address. We also need to be clear what
>> should
>> > happen during Incubation and at what time. I think that many of the
>> > questions that came up in this thread had to do with assessing how
>>much
>> > effort it will take to Incubate Palo (or whatever the name will be)
>> >
>> > (1) The name Palo. Since there seems to be an issue with that name we
>> should
>> > have a new name. It is not unknown for a podling to change its name,
>>but
>> > that does generate extra work for Infrastructure to change the name
>>after
>> > podling start up. It would be our preference for Palo to find a new
>>name
>> > prior to VOTING on the proposal. Please do this elsewhere and come
>>back
>> to
>> > me with the new name so that I can help with the updated proposal.
>> >
>> > (2) Licensing of the software. Several bits came up as questionable.
>> > Regardless of cleanup that has already occurred we have identified
>>that
>> we
>> > will need to be very careful. It will be important to discuss and
>> carefully
>> > handle the Software Grant Agreement to make sure that the source
>>listed
>> is
>> > correct. I think that the SGA must come early during incubation.
>> >
>> > (3) Relationship with Impala. Palo has apparently forked portions of
>> Impala.
>> > This means that some are concerned that there is a missed synergy with
>> the
>> > Apache Impala project. Is there a clean interface that can be built
>> between
>> > the projects? It would help if the Palo developers would explore this
>> with
>> > Impala at d...@impala.apache.org.
>> >
>> > That said, part of the Incubation process is to learn the Apache Way.
>> IMHO
>> > it is ok for the relationship between Impala PMC and a pooling PPMC to
>> be a
>> > work in process.
>> >
>> > (4) Currently, Willem, Luke Han and Dave Fisher are qualified to
>> officially
>> > mentor. I suggest that Sijie Guo and Zheng Shao be included as Initial
>> > Committers in order to help from within the PPMC.
>> >
>> > On Jun 14, 2018, at 11:03 AM, Jim Apple 
>> > wrote:
>> >
>> > I don't want to be a stickler, but I don't think "For issues
>>mentioned by
>> > Jim, Todd and Tim, I have replied on last Saturday."
>> >
>> > To my email about Palo being an ASF project as a storage system
>>without a
>> > query engine, you replied only, &qu

Re: Looking for Champion

[Li,De(BDG)]

Hi Dave,

Thank you for your summary.

For #1, I got it, we will find a new name ASAP within several days.

For #2, I see, about license, we are rechecking all licenses of components in 
Palo, and we have fixed most of those we found as I wrote in last email. Next, 
we will continue to do this work carefully.

For #3, We have reflected upon Jim's suggestion, and we will try to find out or 
define a cleanly interface between Palo and Impala and to determine which parts 
should keep in Palo and which parts should as patches for Impala. More detail 
and roadmap are still to be work out.

For #4, I accepted your suggestion and I will update proposal.

Once I have a new name, I will send you with updated proposal.

Best Regards,
Reed

发件人: Dave Fisher mailto:dave2w...@comcast.net>>
答复: mailto:general@incubator.apache.org>>
日期: 2018年6月19日 星期二 上午2:08
至: mailto:general@incubator.apache.org>>
主题: Re: Looking for Champion

Hi Li,De -

Since I agreed to champion this project I think that we need a summary about 
what the Incubator PMC cares about in order to accept a podling. What the 
prospective project needs to address. We also need to be clear what should 
happen during Incubation and at what time. I think that many of the questions 
that came up in this thread had to do with assessing how much effort it will 
take to Incubate Palo (or whatever the name will be)

(1) The name Palo. Since there seems to be an issue with that name we should 
have a new name. It is not unknown for a podling to change its name, but that 
does generate extra work for Infrastructure to change the name after podling 
start up. It would be our preference for Palo to find a new name prior to 
VOTING on the proposal. Please do this elsewhere and come back to me with the 
new name so that I can help with the updated proposal.

(2) Licensing of the software. Several bits came up as questionable. Regardless 
of cleanup that has already occurred we have identified that we will need to be 
very careful. It will be important to discuss and carefully handle the Software 
Grant Agreement to make sure that the source listed is correct. I think that 
the SGA must come early during incubation.

(3) Relationship with Impala. Palo has apparently forked portions of Impala. 
This means that some are concerned that there is a missed synergy with the 
Apache Impala project. Is there a clean interface that can be built between the 
projects? It would help if the Palo developers would explore this with Impala 
at d...@impala.apache.org<mailto:d...@impala.apache.org>.

That said, part of the Incubation process is to learn the Apache Way. IMHO it 
is ok for the relationship between Impala PMC and a pooling PPMC to be a work 
in process.

(4) Currently, Willem, Luke Han and Dave Fisher are qualified to officially 
mentor. I suggest that Sijie Guo and Zheng Shao be included as Initial 
Committers in order to help from within the PPMC.

On Jun 14, 2018, at 11:03 AM, Jim Apple 
mailto:jbap...@cloudera.com.INVALID>> wrote:

I don't want to be a stickler, but I don't think "For issues mentioned by
Jim, Todd and Tim, I have replied on last Saturday."

To my email about Palo being an ASF project as a storage system without a
query engine, you replied only, "We will seriously consider this proposal."

I see no response to Tim's concern that "The code isn't owned by any
individual, I contributed it to Apache and it's
free for anyone to do what they want to do with it, but pulling in
improvements from other projects without any attempt to attribute it or
contribute improvements back seems contrary to the Apache way.”

Jim - do you need answers to these concerns prior to agreeing to accept this 
project into the Incubator?

Regards,
Dave


On Thu, Jun 14, 2018 at 12:48 AM, Li,De(BDG) 
mailto:l...@baidu.com>> wrote:

Hi all,

About Palo, we have fixed following issues.

1. Related Impala
For issues mentioned by Jim, Todd and Tim, I have replied on last Saturday.

2、Lisence issue
For issues mentioned by Todd and Ted.
1) be/aes/* come from mysql-5.6, GPL v2.1 license
Fixed: removed aes related codes.
https://github.com/baidu/palo/commit/ac770c33d445a4c18a0b74f56b28a4
180b30bf
b7
https://github.com/baidu/palo/commit/3c9f2ae6695ffebe41e39b6bf65440
77698f1c
ed

2) be/util/mysql_dtoa.cpp copy from MySQL, GPL license
Fixed: removed mysql_dtoa related codes.
https://github.com/baidu/palo/commit/bfe1bc7cf39e165a7c52b2c9415509
75b1f841
a1

3) be/http/mongoose.h, Copyright (c) 2004-2012 Sergey Lyubka
Fixed: restored to original lisence, we are searching another http server
to replace it.
https://github.com/baidu/palo/commit/81baef34f48a2dbe7401712c5e0a50
f59f04a8
31

4) be/rpc/*
Fixed: We have replaced it with brpc, and we will remove Hypertable after
few weeks for waiting users' upgrade to brpc.
https://github.com/baidu/palo/tree/master/be/src/rpc

3、Dependency licenses
For issue mentioned by Dave, It looks like 

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: [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: [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>

Re: 20k Github stars for Dubbo

[Li,De(BDG)]

It’s great, congratulations!

On 2018/7/9 下午3:22， "Xin Wang"  wrote:

>Awesome
>
>Zhanhui Li  于2018年7月9日周一 下午2:52写道：
>
>> Congratulations!
>>
>> > 在 2018年7月9日，下午2:42，Mercy  写道：
>> >
>> > Great Job!
>> >
>> >
>> > Kind regards,
>> >
>> > Mercy
>> >
>> >
>> > 在 2018/7/9 上午11:51, Huxing Zhang 写道:
>> >> Hi All,
>> >>
>> >> I am happy to announce that Dubbo has reached 20k Github stars
>> >> today[1], an important milestone for Dubbo.
>> >>
>> >> Dubbo is the first Java project that reaches 20k Github stars[2] in
>> >> Apache Software Foundation, the second most[3] in terms of all
>> >> languages in the foundation.
>> >>
>> >> Dubbo is open sources in 2012, till now, it is the most popular RPC
>> >> framework in China, and has been adopted by many companies for their
>> >> production system, including:
>> >>
>> >> Internet companies:
>> >> * Alibaba
>> >> * Dangdang
>> >> * Qunar
>> >> * Netease
>> >> * etc.
>> >>
>> >> State-owned enterprises:
>> >> * Industrial and Commercial Bank of China
>> >> * China Telecom
>> >> * China Life
>> >> * etc.
>> >>
>> >> More use case can be found at the homepage:
>> http://dubbo.incubator.apache.org/
>> >>
>> >> As an incubator project, the Dubbo PPMC will continue to make the
>> >> community open and diverse, and we are more than happy to have
>> >> everyone come to contribute, any question can be discussed on dev
>> >> mailing list.
>> >>
>> >> [1] https://github.com/apache/incubator-dubbo
>> >> [2]
>> 
>>https://github.com/search?l=Java=desc=org%3Aapache=stars=Repos
>>itories
>> >> [3]
>> 
>>https://github.com/search?o=desc=org%3Aapache=stars=Repositories
>> >>
>> >
>> >
>> >
>> > -
>> > 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] Graduate Apache Griffin (incubating) as a TLP

[Li,De(BDG)]

+1 (non-binding)

On 2018/11/2 上午10:16， "Xin Wang"  wrote:

>+1
>
>Matt Sicker  于2018年11月2日周五 上午12:05写道：
>
>> +1
>>
>> On Thu, 1 Nov 2018 at 07:58, Kevin Yao  wrote:
>>
>> > +1
>> >
>> > On Thu, Nov 1, 2018 at 8:14 PM john@apache  wrote:
>> >
>> > > +1
>> > >
>> > > On Thu, Nov 1, 2018 at 6:03 PM Jean-Baptiste Onofré
>>
>> > > wrote:
>> > >
>> > > > +1 (binding)
>> > > >
>> > > > Regards
>> > > > JB
>> > > >
>> > > > Le 1 nov. 2018 à 14:03, à 14:03, Willem Jiang <
>> willem.ji...@gmail.com>
>> > a
>> > > > écrit:
>> > > > >+1 binding.
>> > > > >It's good to see griffin is ready to graduate.
>> > > > >
>> > > > >Willem Jiang
>> > > > >
>> > > > >Twitter: willemjiang
>> > > > >Weibo: 姜宁willem
>> > > > >
>> > > > >On Thu, Nov 1, 2018 at 3:31 PM William Guo 
>> wrote:
>> > > > >>
>> > > > >> +dev
>> > > > >>
>> > > > >> -- Forwarded message -
>> > > > >> From: William Guo 
>> > > > >> Date: Thu, Nov 1, 2018 at 11:21 AM
>> > > > >> Subject: [VOTE] Graduate Apache Griffin (incubating) as a TLP
>> > > > >> To: 
>> > > > >>
>> > > > >>
>> > > > >> Hi all,
>> > > > >>
>> > > > >> Given that we've got positive feedback on the DISCUSS
>> > > > >> thread, after we had made some changes based on DISCUSS
>>feedback.
>> > > > >> I'd like to start an official VOTE thread now.
>> > > > >>
>> > > > >>
>> > > > >> Please vote on the resolution pasted below to graduate
>> > > > >> Apache Griffin from the incubator to the top level project.
>> > > > >>
>> > > > >> [ ] +1 Graduate Apache Griffin from the Incubator.
>> > > > >> [ ] +0 Don't care.
>> > > > >> [ ] -1 Don't graduate Apache Griffin from the Incubator
>>because...
>> > > > >>
>> > > > >> This vote will be open for at least 72 hours.
>> > > > >>
>> > > > >>
>> > > > >> Many thanks to our mentors and everyone else for their support,
>> > > > >>
>> > > > >> William Guo (on behalf of the Apache Griffin PPMC).
>> > > > >>
>> > > > >>
>> > > > >> ## Resolution to create a TLP from graduating Incubator podling
>> > > > >>
>> > > > >> X. Establish the Apache Griffin Project
>> > > > >>
>> > > > >> WHEREAS, the Board of Directors deems it to be in the best
>> interests
>> > > > >of
>> > > > >> the Foundation and consistent with the Foundation's purpose to
>> > > > >establish
>> > > > >> a Project Management Committee charged with the creation and
>> > > > >maintenance
>> > > > >> of open-source software, for distribution at no charge to the
>> > public,
>> > > > >> related to a data quality solution for big data, including both
>> > > > >streaming
>> > > > >> and batch mode.
>> > > > >>
>> > > > >>
>> > > > >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> Committee
>> > > > >> (PMC), to be known as the "Apache Griffin Project", be and
>>hereby
>> is
>> > > > >> established pursuant to Bylaws of the Foundation; and be it
>> further
>> > > > >>
>> > > > >> RESOLVED, that the Apache Griffin Project be and hereby is
>> > > > >> responsible for the creation and maintenance of software
>>related
>> to
>> > > > >> a data quality solution for big data, including both streaming
>>and
>> > > > >batch
>> > > > >> mode;
>> > > > >> and be it further
>> > > > >>
>> > > > >> RESOLVED, that the office of "Vice President, Apache Griffin"
>>be
>> and
>> > > > >> hereby is created, the person holding such office to serve at
>>the
>> > > > >> direction of the Board of Directors as the chair of the Apache
>> > > > >> Griffin Project, and to have primary responsibility for
>>management
>> > > > >> of the projects within the scope of responsibility of the
>>Apache
>> > > > >> Griffin Project; and be it further
>> > > > >>
>> > > > >> RESOLVED, that the persons listed immediately below be and
>>hereby
>> > are
>> > > > >> appointed to serve as the initial members of the Apache Griffin
>> > > > >Project:
>> > > > >>
>> > > > >> * Alex Lv 
>> > > > >> * Deyi Yao 
>> > > > >> * Eugene Liu 
>> > > > >> * Grant Guo 
>> > > > >> * He Wang 
>> > > > >> * Henry Saputra 
>> > > > >> * Jason Liao 
>> > > > >> * John Liu 
>> > > > >> * Juan Li 
>> > > > >> * Liang Shao 
>> > > > >> * Lionel Liu 
>> > > > >> * Luciano Resende 
>> > > > >> * Nick Sokolov 
>> > > > >> * Shawn Sha 
>> > > > >> * Vincent Zhao 
>> > > > >> * William Guo 
>> > > > >> * Yuqin Xuan 
>> > > > >>
>> > > > >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that William Guo be
>> > > > >> appointed to the office of Vice President, Apache Griffin, to
>> serve
>> > > > >> in accordance with and subject to the direction of the Board of
>> > > > >> Directors and the Bylaws of the Foundation until death,
>> resignation,
>> > > > >> retirement, removal or disqualification, or until a successor
>>is
>> > > > >> appointed; and be it further
>> > > > >>
>> > > > >> RESOLVED, that the Apache Griffin Project be and hereby is
>>tasked
>> > > > >> with the migration and rationalization of the Apache Incubator
>> > > > >> Griffin podling; and be it further
>> > > > >>
>> > > > >> RESOLVED, that all responsibilities pertaining to 

Re: [VOTE] Accept the brpc Project into the Apache Incubator.

[Li,De(BDG)]

+1 (non-binding)

The brpc is very broadly used in Baidu, and I’m sure it will benefit to
many projects too.

On 2018/11/9 上午9:04， "Willem Jiang"  wrote:

>+1(binding)
>
>Willem Jiang
>
>Twitter: willemjiang
>Weibo: 姜宁willem
>
>On Fri, Nov 9, 2018 at 3:28 AM Dave Fisher  wrote:
>>
>> Hi -
>>
>> This is a VOTE to accept the brpc Project into the Apache Incubator.
>>
>> It will last for at least 72 hours and will pass if at least 3 +1 IPMC
>>Votes and more IPMC Votes are +1 than -1.
>>
>> [ ] +1, accept the brpc proposal.
>> [ ] -1, reject the brpc proposal
>>
>> Regards,
>> Dave
>>
>> = brpc Proposal =
>>
>> === Abstract ===
>>
>> brpc is an industrial-grade RPC framework for building reliable and
>>high-performance services.
>>
>>
>> === Proposal ===
>>
>> We propose to contribute the brpc codebase and associated
>>artifacts(e.g. documentation etc.) to the Apache Software Foundation,
>>and aim to  build a wider open community around it in the 'Apache Way'.
>>
>> === Background ===
>>
>> The RPC framework used in Baidu before 2014 was developed at 2008 and
>>limited in protocols and performance, and there were also serveral
>>implementations focused on their own scenarios from Baidu's different
>>BU. As an infrastructural team in Baidu, we tried to build a new
>>framework to unify all RPC scenarios inside. The framework was named
>>"baidu-rpc" internally the early versions were adopted and online at
>>late 2014. The framework was rapidly iterated at 2015-2017, and
>>thousands kinds of services and almost all core services adopted it. And
>>in 2017, we opensourced it as "brpc" and hope to get more adoptions and
>>contributions from outside. At the time of opensourcing, there're more
>>than 1 million instances inside Baidu using baidu-rpc (not counting
>>clients).
>>
>>
>> === Rationale ===
>>
>> brpc has been approved inside baidu, since many high performance core
>>services are using it.
>> And since its open source, it has been adopted by several other
>>companies, including Iqiyi, Didi, Sougou, BiliBili etc.
>>
>>
>> === Current Status ===
>>
>> brpc has been an open source project on GitHub
>>(https://github.com/brpc/brpc ) since 2017.
>>
>> Currently it has more than 7.3k stars, 1.6k forks, and is one of the
>>most popular repositories in topic of rpc category in GitHub rpc
>>catelogy.
>> It has been widely used in Baidu, with 1,000,000+ instances and
>>thousands kinds of services.
>> Besides, many other companies have already used it also, such as Iqiyi,
>>Didi, Sougou, BiliBili etc.
>>
>>
>> === Meritocracy ===
>>
>> brpc was originally created by Ge Jun and Chen zhangyi inside baidu
>>from 2014.
>> Since its opensource in 2017, it has already followed meritocracy
>>principles.
>> It accepts multiple contributions from other companies.
>> And now, the core developers are from several different companies.
>>
>> We will follow Apache way to encourage more developers to contribute in
>>this project.
>> We know that only active and committed developers from a diverse set of
>>backgrounds
>> can make brpc a successful project.
>>
>>
>> === Community ===
>>
>> brpc has been building an active community since its open source.
>>Currently,
>> the community includes over 31 contributors.
>> The core developers of brpc are listed below.
>>
>> === Core Developers ===
>>
>>   * Ge Jun(https://github.com/jamesge 
>>jge...@gmail.com )
>>   * Chen Zhangyi(https://github.com/chenzhangyi
>> frozen@gmail.com
>>)
>>   * Jiang Rujie(https://github.com/old-bear
>> jrjb...@gmail.com
>>)
>>   * Zhu Jiashun(http://github.com/zyearn 
>>zhujiashun2...@gmail.com )
>>   * Wang Yao(https://github.com/ipconfigme
>> ipconfi...@gmail.com
>>)
>>
>> === Alignment ===
>>
>> brpc is useful for building reliable and high-performance applications.
>> Since ASF has many famous performance-related and rpc-related projects,
>> we believe that ASF is a perfect choice to help brpc project to attract
>> more developers and users as well as having more cooperation with
>>existing projects.
>>
>> === Known Risks ===
>>  Orphaned products 
>>
>> Since our core developers are from different companies and many
>>companies are using it,
>> the risk of the project being abandoned is minimal.
>> For example, Baidu is extensively using it in their production
>>environment
>> and many large corporations including Iqiyi, Didi, Sougou, BiliBili use
>>it in their production applications.
>>
>>  Inexperience with Open Source 
>>
>> brpc has been an active open source project for more than one year.
>> During that time, the project has attracted 30+ contributors and gained
>>a lot of attention.
>> The core developers are all 

Re: [VOTE] Graduate Apache ServiceComb (incubating)

[Li,De(BDG)]

+1(non-binding)

Best Regards,
Reed



On 2018/9/28 上午10:51， "Yang Bo"  wrote:

>+1 non-binding
>
>On Fri, Sep 28, 2018 at 10:00 AM Zen Lin 
>wrote:
>
>> +1  (non-binding)
>> Best Regards,
>> ---
>> Zen Lin
>> zenlintechnofr...@gmail.com
>> Focused on Micro Service and Apache ServiceComb
>>
>>
>> Liu Guo <13493...@qq.com> 于2018年9月27日周四 下午10:04写道：
>>
>> > +1 (non-binding)
>> >
>> >
>> > -- Original --
>> > From: Gangumalla, Uma 
>> > Date: Thu,Sep 27,2018 2:44 AM
>> > To: general@incubator.apache.org 
>> > Subject: Re: RE: [VOTE] Graduate Apache ServiceComb (incubating)
>> >
>> >
>> >
>> > +1 (binding)
>> >
>> > Regards,
>> > Uma
>> >
>> > -Original Message-
>> > From: Dave Fisher [mailto:dave2w...@comcast.net]
>> > Sent: Wednesday, September 26, 2018 11:31 AM
>> > To: general@incubator.apache.org
>> > Subject: Re: [VOTE] Graduate Apache ServiceComb (incubating)
>> >
>> > +1 (binding)
>> >
>> > > On Sep 26, 2018, at 12:06 AM, Roman Shaposhnik 
>>wrote:
>> > >
>> > > Hi!
>> > >
>> > > given that we've got only positive feedback on the DISCUSS thread
>>I'd
>> > > like to start an official VOTE thread now.
>> > >
>> > > Please vote on the resolution pasted below to graduate Apache
>> > > ServiceComb from the incubator to the top level project.
>> > >
>> > > [ ] +1 Graduate Apache ServiceComb from the Incubator.
>> > > [ ] +0 Don't care.
>> > > [ ] -1 Don't graduate Apache ServiceComb from the Incubator
>>because...
>> > >
>> > > This vote will be open for at least 72 hours.
>> > >
>> > > Many thanks to our mentors and everyone else for their support,
>>Roman
>> > > (on behalf of the Apache ServiceComb PPMC).
>> > >
>> > > ## Resolution to create a TLP from graduating Incubator podling
>> > >
>> > > X. Establish the Apache ServiceComb Project
>> > >
>> > > WHEREAS, the Board of Directors deems it to be in the best interests
>> > > of the Foundation and consistent with the Foundation's purpose to
>> > > establish a Project Management Committee charged with the creation
>>and
>> > > maintenance of open-source software, for distribution at no charge
>>to
>> > > the public, related to a microservice framework that provides a set
>>of
>> > > tools and components to make development and deployment of cloud
>> > > applications easier.
>> > >
>> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> > > (PMC), to be known as the "Apache ServiceComb Project", be and
>>hereby
>> > > is established pursuant to Bylaws of the Foundation; and be it
>>further
>> > >
>> > > RESOLVED, that the Apache ServiceComb Project be and hereby is
>> > > responsible for the creation and maintenance of software related to
>>a
>> > > microservice framework that provides a set of tools and components
>>to
>> > > make development and deployment of cloud applications easier; and be
>> > > it further
>> > >
>> > > RESOLVED, that the office of "Vice President, Apache ServiceComb" be
>> > > and hereby is created, the person holding such office to serve at
>>the
>> > > direction of the Board of Directors as the chair of the Apache
>> > > ServiceComb Project, and to have primary responsibility for
>>management
>> > > of the projects within the scope of responsibility of the Apache
>> > > ServiceComb Project; and be it further
>> > >
>> > > RESOLVED, that the persons listed immediately below be and hereby
>>are
>> > > appointed to serve as the initial members of the Apache ServiceComb
>> > > Project:
>> > >
>> > > * Aray Chenchu Sukesh 
>> > > * Bao Liu 
>> > > * Eric Lee 
>> > > * Jean-Baptiste Onofré 
>> > > * Jimin Wu 
>> > > * Linzhinan 
>> > > * Mohammad Asif Siddiqui 
>> > > * Qi Zhang 
>> > > * Roman Shaposhnik 
>> > > * Timothy Chen 
>> > > * Willem Ning Jiang 
>> > > * Yang Bo 
>> > > * Yihua Cui 
>> > > * Yin Xiang 
>> > > * Zheng Feng 
>> > > * zhengyangyong 
>> > >
>> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Willem Ning Jiang be
>> > > appointed to the office of Vice President, Apache ServiceComb, to
>> > > serve in accordance with and subject to the direction of the Board
>>of
>> > > Directors and the Bylaws of the Foundation until death, resignation,
>> > > retirement, removal or disqualification, or until a successor is
>> > > appointed; and be it further
>> > >
>> > > RESOLVED, that the Apache ServiceComb Project be and hereby is
>>tasked
>> > > with the migration and rationalization of the Apache Incubator
>> > > ServiceComb podling; and be it further
>> > >
>> > > RESOLVED, that all responsibilities pertaining to the Apache
>>Incubator
>> > > ServiceComb podling encumbered upon the Apache Incubator PMC are
>> > > hereafter discharged.
>> > >
>> > > 
>>-
>> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > > For additional commands, e-mail: general-h...@incubator.apache.org
>> > >
>> >
>> >
>> > -
>> > To 

[Wiki] Request permissions to file reports

[Li,De(BDG)]

Hi -

I need to file reports of Doris Podling for Incubator Wiki 
(https://wiki.apache.org/incubator/September2018).
Would someone please enable my account "reed".

Best regards,
Reed

[Wiki] Request permissions to file reports

[Li,De(BDG)]

Hi -

I need to file reports of Doris Podling for Incubator Wiki 
(https://wiki.apache.org/incubator/September2018).
Would someone please enable my account "reed".

Best regards,
Reed

Re: [VOTE] Release Apache Doris 0.9.0-incubating-rc01

[Li,De(BDG)]

Thanks to Willem and Justin,

For building issue, we will update build script and README to clear that
Doris cannot support Mac OSX currently.
For license issue, we will fix them as Willem said.

Best Regards
Reed

On 2018/12/22 上午10:10， "Willem Jiang"  wrote:

>Hi,
>
>I tried to build the kit in my Mac OSX,  I got the GCC version error.
>I think we need to update the README for it.
>I checked the License file and have some concerns about them.
>
>1. We cannot add the ASL license header on[1][2],we need to keep the
>third part header there[3]
>2. I can not find the files of [4][5], which are specified on the
>License file, please remove them.
>3. For files in [6], it's hard to tell which file is using ASL 2.0 or
>BSD License, maybe you need to keep the original License reference of
>Chromium.
>
>[1]be/src/runtime/string_search.hpp
>[2]be/src/util/murmur_hash3.cpp
>[3]https://www.apache.org/legal/src-headers.html#3party
>[4]be/src/util/new_status.cpp
>[5]be/src/util/new_status.h
>[6]be/src/gutil
>
>Willem Jiang
>
>Twitter: willemjiang
>Weibo: 姜宁willemOn Thu, Dec 20, 2018 at 2:32 PM 德 李 
>wrote:
>>
>> Hi all,
>>
>> Please review and vote on Apache Doris 0.9.0-incubating-rc01 release.
>>
>> Apache Doris is an MPP-based interactive SQL data warehousing for
>>reporting
>> and analysis.
>>
>> The Apache Doris community has voted on and approved this release:
>> 
>>https://lists.apache.org/thread.html/66af86fb92784eada8bc7690b5aa8962b6d4
>>798
>> 5cf9182240f65cda5@%3Cdev.doris.apache.org%3E
>>
>> The vote result email thread:
>> 
>>https://lists.apache.org/thread.html/fd06ae12f6cc47bb11c8408a5825a291c095
>>98f
>> 1ee15dfa19b667f8b@%3Cdev.doris.apache.org%3E
>>
>> The release candidate has been tagged in GitHub as 0.9.0-rc01, available
>> here:
>> https://github.com/apache/incubator-doris/releases/tag/0.9.0-rc01
>>
>> There is no CHANGE LOG file because this is the first release of Apache
>> Doris.
>> Thanks to everyone who has contributed to this release, and there is a
>> simple release notes can be found here:
>> https://github.com/apache/incubator-doris/issues/406
>>
>> The artifacts (source, signature and checksum) corresponding to this
>>release
>> candidate can be found here:
>> 
>>https://dist.apache.org/repos/dist/dev/incubator/doris/0.9.0-incubating-r
>>c01
>> /
>>
>> This has been signed with PGP key 33DBF2E0, corresponding to
>> l...@apache.org.
>> KEYS file is available here:
>> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS
>> It is also listed here:
>> https://people.apache.org/keys/committer/lide.asc
>>
>> To verify and build, you can refer to following wiki:
>> 
>>https://github.com/apache/incubator-doris/wiki/How-to-verify-Apache-Relea
>>se
>> 
>>https://github.com/apache/incubator-doris/blob/master/README.md#42-for-li
>>nux
>>
>> The vote will be open for at least 72 hours.
>> [ ] +1 Approve the release
>> [ ] +0 No opinion
>> [ ] -1 Do not release this package because ...
>>
>> Best Regards,
>>
>> Reed
>>
>>
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: [VOTE] Release Apache Doris 0.9.0-incubating-rc01

[Li,De(BDG)]

Thanks to David, could you provide the detail for failure, actually, we
expect building is OK if following tools installed on Ubuntu.

GCC 5.3.1+, Oracle JDK 1.8+, Python 2.7+, Apache Maven 3.5+, CMake 3.4.3+


Best Regards,
Reed

On 2018/12/27 上午4:52， "David Meikle"  wrote:

>As Willem outlined, there is a few of minor header issues to fix but
>looks good.  I checked; Name, Sig and Hashes, Notice, License.
>
>I tried to build on Ubuntu 18.10 following the instructions in the README
>but it fails.  Is this expected?
>
>Would be happy to +1 if we are comfortable the source build “builds” as
>intended.
>
>Cheers,
>Dave
>
>> On 20 Dec 2018, at 06:32, 德 李  wrote:
>> 
>> The vote will be open for at least 72 hours.
>> [ ] +1 Approve the release
>> [ ] +0 No opinion
>> [ ] -1 Do not release this package because ...
>> 
>> Best Regards,
>> 
>> Reed
>

Re: [VOTE] Release Apache Doris 0.9.0-incubating-rc01

[Li,De(BDG)]

Hi Dave,

Thanks for your reply.

The files of flat_map.h and json_to_pb.h are come from brpc, which should
be installed in thirdparty/installed/include.


It seems brpc is not been compiled and installed successfully.

Could you remove brpc and retry build as following command ? It will help
us to know what happed.


$ cd 
/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-0.9.
0.rc01-incubating-src
$ rm -f thirdparty/installed/lib/librdkafka.a
$ rm -fr thirdparty/src/brpc-0.9.0*
$ sh build.sh

Regards,
Reed

On 2018/12/27 下午6:33， "David Meikle"  wrote:

>Hi Reed,
>
>> On 27 Dec 2018, at 03:00, Li,De(BDG)  wrote:
>> 
>> Thanks to David, could you provide the detail for failure, actually, we
>> expect building is OK if following tools installed on Ubuntu.
>> 
>> GCC 5.3.1+, Oracle JDK 1.8+, Python 2.7+, Apache Maven 3.5+, CMake
>>3.4.3+
>> 
>> 
>> Best Regards,
>> Reed
>
>
>
>I get the following errors:
>
>-- CLANG_COMPATIBLE_FLAGS: -I/usr/include/c++/7
>-I/usr/include/x86_64-linux-gnu/c++/7 -I/usr/include/c++/7/backward
>-I/usr/lib/gcc/x86_64-linux-gnu/7/include -I/usr/local/include
>-I/usr/lib/gcc/x86_64-linux-gnu/7/include-fixed
>-I/usr/include/x86_64-linux-gnu -I/usr/include
>-- Configuring done
>-- Generating done
>-- Build files have been written to:
>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-0.9
>.0.rc01-incubating-src/be/build
>[  1%] Built target gen_ir_descriptions
>[  2%] Built target Udf
>[  3%] Built target Common
>[ 14%] Built target Util
>[ 23%] Built target Exprs
>[ 32%] Built target Gutil
>[ 46%] Built target DorisGen
>[ 48%] Built target Agent
>[ 48%] Building CXX object
>src/http/CMakeFiles/Webserver.dir/ev_http_server.cpp.o
>[ 49%] Building CXX object
>src/olap/CMakeFiles/Olap.dir/olap_header_manager.cpp.o
>In file included from
>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-0.9
>.0.rc01-incubating-src/be/src/http/ev_http_server.cpp:31:0:
>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-0.9
>.0.rc01-incubating-src/be/src/service/brpc.h:50:10: fatal error:
>butil/containers/flat_map.h: No such file or directory
> #include 
>  ^
>compilation terminated.
>src/http/CMakeFiles/Webserver.dir/build.make:350: recipe for target
>'src/http/CMakeFiles/Webserver.dir/ev_http_server.cpp.o' failed
>make[2]: *** [src/http/CMakeFiles/Webserver.dir/ev_http_server.cpp.o]
>Error 1
>CMakeFiles/Makefile2:581: recipe for target
>'src/http/CMakeFiles/Webserver.dir/all' failed
>make[1]: *** [src/http/CMakeFiles/Webserver.dir/all] Error 2
>make[1]: *** Waiting for unfinished jobs
>[ 49%] Building CXX object src/olap/CMakeFiles/Olap.dir/olap_meta.cpp.o
>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-0.9
>.0.rc01-incubating-src/be/src/olap/olap_header_manager.cpp:30:10: fatal
>error: json2pb/json_to_pb.h: No such file or directory
> #include "json2pb/json_to_pb.h"
>  ^~
>compilation terminated.
>src/olap/CMakeFiles/Olap.dir/build.make:806: recipe for target
>'src/olap/CMakeFiles/Olap.dir/olap_header_manager.cpp.o' failed
>make[2]: *** [src/olap/CMakeFiles/Olap.dir/olap_header_manager.cpp.o]
>Error 1
>make[2]: *** Waiting for unfinished jobs
>CMakeFiles/Makefile2:471: recipe for target
>'src/olap/CMakeFiles/Olap.dir/all' failed
>make[1]: *** [src/olap/CMakeFiles/Olap.dir/all] Error 2
>Makefile:129: recipe for target 'all' failed
>make: *** [all] Error 2
>
>Cheers,
>Dave

Re: [VOTE] Release Apache Doris 0.9.0-incubating-rc01

[Li,De(BDG)]

Hi,

Does anyone help us to check and vote？
Now we got two +1(binding).
If needed we will cancel and call for next VOTE after fixed all issues
which Willem and Justin mentioned.


Best Regards,
Reed

On 2018/12/29 上午10:36， "Li,De(BDG)"  wrote:

>Hi Dave,
>
>I got it, thank you very much. Have a good trip.
>
>Best Regards,
>Reed
>
>On 2018/12/28 下午10:49， "Dave Meikle"  wrote:
>
>>Hi Reed,
>>
>>I am traveling just now so away from the desktop that I tested the build
>>on.  I setup a clean virtual machine with Ubuntu 18.04 and tried from
>>scratch, resulting in a perfect build.  So must be something funky with
>>my
>>configuration back at base - it's been upgraded a few times, so sorry for
>>the hassle.
>>
>>(NOTE: I tried to build on a remote Ubuntu 18.10 at first getting a
>>different error but it made sense due to the 3rd-party LLVM fails due to
>>ustat depreciation in glibc).
>>
>>So +1 (binding) to the release.
>>
>>Cheers,
>>Dave
>>
>>On Thu, 27 Dec 2018 at 12:13, Li,De(BDG)  wrote:
>>
>>> Hi Dave,
>>>
>>> Thanks for your reply.
>>>
>>> The files of flat_map.h and json_to_pb.h are come from brpc, which
>>>should
>>> be installed in thirdparty/installed/include.
>>>
>>>
>>> It seems brpc is not been compiled and installed successfully.
>>>
>>> Could you remove brpc and retry build as following command ? It will
>>>help
>>> us to know what happed.
>>>
>>>
>>> $ cd
>>> 
>>>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-0
>>>.
>>>9.
>>> 0.rc01-incubating-src
>>> $ rm -f thirdparty/installed/lib/librdkafka.a
>>> $ rm -fr thirdparty/src/brpc-0.9.0*
>>> $ sh build.sh
>>>
>>> Regards,
>>> Reed
>>>
>>> On 2018/12/27 下午6:33， "David Meikle"  wrote:
>>>
>>> >Hi Reed,
>>> >
>>> >> On 27 Dec 2018, at 03:00, Li,De(BDG)  wrote:
>>> >>
>>> >> Thanks to David, could you provide the detail for failure, actually,
>>>we
>>> >> expect building is OK if following tools installed on Ubuntu.
>>> >>
>>> >> GCC 5.3.1+, Oracle JDK 1.8+, Python 2.7+, Apache Maven 3.5+, CMake
>>> >>3.4.3+
>>> >>
>>> >>
>>> >> Best Regards,
>>> >> Reed
>>> >
>>> >
>>> >
>>> >I get the following errors:
>>> >
>>> >-- CLANG_COMPATIBLE_FLAGS: -I/usr/include/c++/7
>>> >-I/usr/include/x86_64-linux-gnu/c++/7 -I/usr/include/c++/7/backward
>>> >-I/usr/lib/gcc/x86_64-linux-gnu/7/include -I/usr/local/include
>>> >-I/usr/lib/gcc/x86_64-linux-gnu/7/include-fixed
>>> >-I/usr/include/x86_64-linux-gnu -I/usr/include
>>> >-- Configuring done
>>> >-- Generating done
>>> >-- Build files have been written to:
>>> 
>>>>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-
>>>>0
>>>>.9
>>> >.0.rc01-incubating-src/be/build
>>> >[  1%] Built target gen_ir_descriptions
>>> >[  2%] Built target Udf
>>> >[  3%] Built target Common
>>> >[ 14%] Built target Util
>>> >[ 23%] Built target Exprs
>>> >[ 32%] Built target Gutil
>>> >[ 46%] Built target DorisGen
>>> >[ 48%] Built target Agent
>>> >[ 48%] Building CXX object
>>> >src/http/CMakeFiles/Webserver.dir/ev_http_server.cpp.o
>>> >[ 49%] Building CXX object
>>> >src/olap/CMakeFiles/Olap.dir/olap_header_manager.cpp.o
>>> >In file included from
>>> 
>>>>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-
>>>>0
>>>>.9
>>> >.0.rc01-incubating-src/be/src/http/ev_http_server.cpp:31:0:
>>> 
>>>>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-
>>>>0
>>>>.9
>>> >.0.rc01-incubating-src/be/src/service/brpc.h:50:10: fatal error:
>>> >butil/containers/flat_map.h: No such file or directory
>>> > #include 
>>> >  ^
>>> >compilation terminated.
>>> >src/http/CMakeFiles/Webserver.dir/build.make:350: recipe for target
>>> >'src/http/CMakeFiles/Webserver.dir/ev_http_server.cpp.o' failed
>>> >make[2]: *** [src/http/CMakeFiles/Web

Re: [VOTE] Release Apache Doris 0.9.0-incubating-rc01

[Li,De(BDG)]

Hi Makoto,

Thank you for your check.

>> Why not cancel rc1 and create rc2 fixing license header issue that
Willem
>> pointed?
>> It seems it's better to be fixed.

Actually, we have fixed these issues in branch-0.9.0 (#471, #473) after
Willem pointed.

I’m afraid it will take everyone’s more time to check repeatedly and so
I’m going to fix them in next version.

>> It also seems that no one from IPMC succeeded to build distribution
from src

Indeed, the building is not good as we expect, but I noticed the main
cause is that it can’t compile in OSX and it needs GCC 5.3.1+.
But it seems Dave Meikle has succeeded to build in Ubuntu 18.04 and we
have tested pass in CentOS and Ubuntu.
We will continue to check and complete the building, also docker
environment as you mentioned.

Best Regards,
Reed


On 2019/1/11 上午2:23， "Makoto Yui"  wrote:

>Reed,
>
>Why not cancel rc1 and create rc2 fixing license header issue that Willem
>pointed?
>It seems it's better to be fixed.
>
>It also seems that no one from IPMC succeeded to build distribution from
>src (no sure for Luke though).
>
>I got the following build error (which might be gcc-5 version issue):
>
>[ 57%] Building CXX object
>projects/compiler-rt/lib/msan/CMakeFiles/clang_rt.msan-x86_64.dir/msan_int
>erceptors.cc.o
>
>/tmp/doris/apache-doris-0.9.0.rc01-incubating-src/thirdparty/src/llvm-3.4.
>2.src/projects/compiler-rt/lib/msan/msan_interceptors.cc:
>In function 'void __msan::InitializeInterceptors()':
>
>/tmp/doris/apache-doris-0.9.0.rc01-incubating-src/thirdparty/src/llvm-3.4.
>2.src/projects/compiler-rt/lib/msan/msan_interceptors.cc:1573:1:
>internal
>compiler error: Segmentation fault
>
> }
>
> ^
>
>Please submit a full bug report,
>
>with preprocessed source if appropriate.
>
>See  for instructions.
>
>projects/compiler-rt/lib/msan/CMakeFiles/clang_rt.msan-x86_64.dir/build.ma
>ke:134:
>recipe for target
>'projects/compiler-rt/lib/msan/CMakeFiles/clang_rt.msan-x86_64.dir/msan_in
>terceptors.cc.o'
>failed
>
>I used ubuntu xenial on docker on OSX.
>Software versions meets requirements (except Maven version) as seen in
>
>docker run ubuntu:xenial -it
>
>
>$ apt-get install wget openjdk-8-jdk maven gcc-5 bzip2 python cmake zip
>xz-utils patch byacc flex automake libtool g++
>
>
>root@d9e5b7017e7b:/tmp/doris/apache-doris-0.9.0.rc01-incubating-src# gcc
>--version | head -1
>
>gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609
>
>
>root@d9e5b7017e7b:/tmp/doris/apache-doris-0.9.0.rc01-incubating-src# java
>-version
>
>openjdk version "1.8.0_191"
>
>OpenJDK Runtime Environment (build
>1.8.0_191-8u191-b12-0ubuntu0.16.04.1-b12)
>
>OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)
>
>
>root@d9e5b7017e7b:/tmp/doris/apache-doris-0.9.0.rc01-incubating-src#
>python
>--version
>
>Python 2.7.12
>
>
>root@d9e5b7017e7b:/tmp/doris/apache-doris-0.9.0.rc01-incubating-src# mvn
>--version
>
>Apache Maven 3.3.9
>
>
>root@d9e5b7017e7b:/tmp/doris/apache-doris-0.9.0.rc01-incubating-src# cmake
>--version
>
>cmake version 3.5.1
>
>
>$ ./build.sh
>
>
>
>Providing working Dockerfile would help to verify release by IPMC members.
>
>Thanks,
>Makoto
>
>2019年1月10日(木) 15:51 Li,De(BDG) :
>>
>> Hi,
>>
>> Does anyone help us to check and vote？
>> Now we got two +1(binding).
>> If needed we will cancel and call for next VOTE after fixed all issues
>> which Willem and Justin mentioned.
>>
>>
>> Best Regards,
>> Reed
>>
>> On 2018/12/29 上午10:36， "Li,De(BDG)"  wrote:
>>
>> >Hi Dave,
>> >
>> >I got it, thank you very much. Have a good trip.
>> >
>> >Best Regards,
>> >Reed
>> >
>> >On 2018/12/28 下午10:49， "Dave Meikle"  wrote:
>> >
>> >>Hi Reed,
>> >>
>> >>I am traveling just now so away from the desktop that I tested the
>>build
>> >>on.  I setup a clean virtual machine with Ubuntu 18.04 and tried from
>> >>scratch, resulting in a perfect build.  So must be something funky
>>with
>> >>my
>> >>configuration back at base - it's been upgraded a few times, so sorry
>for
>> >>the hassle.
>> >>
>> >>(NOTE: I tried to build on a remote Ubuntu 18.10 at first getting a
>> >>different error but it made sense due to the 3rd-party LLVM fails due
>>to
>> >>ustat depreciation in glibc).
>> >>
>> >>So +1 (binding) to the release.
>> >>
>> >>Cheers,
>> >>Dave
&

Re: [VOTE] Release Apache Doris 0.9.0-incubating-rc01

[Li,De(BDG)]

Hi Dave,

I got it, thank you very much. Have a good trip.

Best Regards,
Reed

On 2018/12/28 下午10:49， "Dave Meikle"  wrote:

>Hi Reed,
>
>I am traveling just now so away from the desktop that I tested the build
>on.  I setup a clean virtual machine with Ubuntu 18.04 and tried from
>scratch, resulting in a perfect build.  So must be something funky with my
>configuration back at base - it's been upgraded a few times, so sorry for
>the hassle.
>
>(NOTE: I tried to build on a remote Ubuntu 18.10 at first getting a
>different error but it made sense due to the 3rd-party LLVM fails due to
>ustat depreciation in glibc).
>
>So +1 (binding) to the release.
>
>Cheers,
>Dave
>
>On Thu, 27 Dec 2018 at 12:13, Li,De(BDG)  wrote:
>
>> Hi Dave,
>>
>> Thanks for your reply.
>>
>> The files of flat_map.h and json_to_pb.h are come from brpc, which
>>should
>> be installed in thirdparty/installed/include.
>>
>>
>> It seems brpc is not been compiled and installed successfully.
>>
>> Could you remove brpc and retry build as following command ? It will
>>help
>> us to know what happed.
>>
>>
>> $ cd
>> 
>>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-0.
>>9.
>> 0.rc01-incubating-src
>> $ rm -f thirdparty/installed/lib/librdkafka.a
>> $ rm -fr thirdparty/src/brpc-0.9.0*
>> $ sh build.sh
>>
>> Regards,
>> Reed
>>
>> On 2018/12/27 下午6:33， "David Meikle"  wrote:
>>
>> >Hi Reed,
>> >
>> >> On 27 Dec 2018, at 03:00, Li,De(BDG)  wrote:
>> >>
>> >> Thanks to David, could you provide the detail for failure, actually,
>>we
>> >> expect building is OK if following tools installed on Ubuntu.
>> >>
>> >> GCC 5.3.1+, Oracle JDK 1.8+, Python 2.7+, Apache Maven 3.5+, CMake
>> >>3.4.3+
>> >>
>> >>
>> >> Best Regards,
>> >> Reed
>> >
>> >
>> >
>> >I get the following errors:
>> >
>> >-- CLANG_COMPATIBLE_FLAGS: -I/usr/include/c++/7
>> >-I/usr/include/x86_64-linux-gnu/c++/7 -I/usr/include/c++/7/backward
>> >-I/usr/lib/gcc/x86_64-linux-gnu/7/include -I/usr/local/include
>> >-I/usr/lib/gcc/x86_64-linux-gnu/7/include-fixed
>> >-I/usr/include/x86_64-linux-gnu -I/usr/include
>> >-- Configuring done
>> >-- Generating done
>> >-- Build files have been written to:
>> 
>>>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-0
>>>.9
>> >.0.rc01-incubating-src/be/build
>> >[  1%] Built target gen_ir_descriptions
>> >[  2%] Built target Udf
>> >[  3%] Built target Common
>> >[ 14%] Built target Util
>> >[ 23%] Built target Exprs
>> >[ 32%] Built target Gutil
>> >[ 46%] Built target DorisGen
>> >[ 48%] Built target Agent
>> >[ 48%] Building CXX object
>> >src/http/CMakeFiles/Webserver.dir/ev_http_server.cpp.o
>> >[ 49%] Building CXX object
>> >src/olap/CMakeFiles/Olap.dir/olap_header_manager.cpp.o
>> >In file included from
>> 
>>>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-0
>>>.9
>> >.0.rc01-incubating-src/be/src/http/ev_http_server.cpp:31:0:
>> 
>>>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-0
>>>.9
>> >.0.rc01-incubating-src/be/src/service/brpc.h:50:10: fatal error:
>> >butil/containers/flat_map.h: No such file or directory
>> > #include 
>> >  ^
>> >compilation terminated.
>> >src/http/CMakeFiles/Webserver.dir/build.make:350: recipe for target
>> >'src/http/CMakeFiles/Webserver.dir/ev_http_server.cpp.o' failed
>> >make[2]: *** [src/http/CMakeFiles/Webserver.dir/ev_http_server.cpp.o]
>> >Error 1
>> >CMakeFiles/Makefile2:581: recipe for target
>> >'src/http/CMakeFiles/Webserver.dir/all' failed
>> >make[1]: *** [src/http/CMakeFiles/Webserver.dir/all] Error 2
>> >make[1]: *** Waiting for unfinished jobs
>> >[ 49%] Building CXX object src/olap/CMakeFiles/Olap.dir/olap_meta.cpp.o
>> 
>>>/home/dmeikle/Development/Apache/incubator/release-review/apache-doris-0
>>>.9
>> >.0.rc01-incubating-src/be/src/olap/olap_header_manager.cpp:30:10: fatal
>> >error: json2pb/json_to_pb.h: No such file or directory
>> > #include "json2pb/json_to_pb.h"
>> >  ^~
>> >compilation terminated.
>> >src/olap/CMakeFiles/Olap.dir/build.make:806: recipe for target
>> >'src/olap/CMakeFiles/Olap.dir/olap_header_manager.cpp.o' failed
>> >make[2]: *** [src/olap/CMakeFiles/Olap.dir/olap_header_manager.cpp.o]
>> >Error 1
>> >make[2]: *** Waiting for unfinished jobs
>> >CMakeFiles/Makefile2:471: recipe for target
>> >'src/olap/CMakeFiles/Olap.dir/all' failed
>> >make[1]: *** [src/olap/CMakeFiles/Olap.dir/all] Error 2
>> >Makefile:129: recipe for target 'all' failed
>> >make: *** [all] Error 2
>> >
>> >Cheers,
>> >Dave
>>
>>

Re: [VOTE] Release Apache Doris 0.9.0-incubating-rc02

[Li,De(BDG)]

Thank you, Justin, we will fix the license issue in next release.

On 2019/2/14 上午10:39， "Justin Mclean"  wrote:

>Hi,
>
>+1 binding but LICENSE is missing a couple of licenses please fix in next
>release.
>
>Checked:
>- incubating in name
>- hashes and signatures good
>- LICENSE is missing some licenses (se below)
>- NOTICE is fine
>- No unexpected binaries in file
>- All ASF source files have ASF headers
>- On OSX so didn’t build
>
>LICENSE is missing MIT licensed Sizzle.js [1] included in jQuery and MIT
>licensed normalize.css included in bootstrap.css.
>
>Thanks.
>Justin
>
>1. ./webroot/static/jquery.js
>2. ./webroot/static/bootstrap.css
>
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>