calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Juan Pan" <>
Subject Re: [DISCUSS] State of the project 2019
Date Wed, 23 Oct 2019 04:40:05 GMT
Hi everyone,

Actually i think it's time to have my say after receiving the email titiled `Have your say!`
from Julian Hyde.

As a person new this project, i am appreciated community's help for my question ml, and glad
to see its communnity so active and harmonious. Other than that, it also gives me some new
ideas for our incubator project. As of now, i am exploring Calcite, so if possible, i want
to do some contributions to it as well.

Hope Apache Calcite better and better in future.

Best wishes,

 Juan Pan
Juan Pan(Trista), Apache ShardingSphere

On 10/23/2019 11:21,Chunwei Lei<> wrote:
Thank you for your great work, Francis!

In the past year, I deeply feel that Calcite community is becoming more and
more active, which means that more and
more companies start to use Apache Calcite. This is very exciting and

Thanks to active contributions and committers, pull requests could be
reviewed and merged in a short time currently
which really benefits a lot.

I also feel that there are quite a few tough legacy issues left. I hope we
can spend more time discussing and finding out
a solution in the future.



On Wed, Oct 23, 2019 at 9:38 AM Danny Chan <> wrote:

Thanks for the state summarize Francis Chuang ! And thanks for the awesome
work for keeping Calcite in good shape !

From my perspective, I really feel that Calcite is becoming more and more
popular and there are many new groups trying to use this great project, as
a reviewer, I saw many contributions from all kinds of people. And I feel
very proud of that !

For the last year, I did many work to let Apache Flink and Calcite to have
better integration, and I believe there would be more and more people to
make contributions and make Calcite more pluggable and more suitable for
production environments !

I also very enjoy the absolute harmony of the community, we are fire
interesting discussions on the mailing list and we did have some valuable
conclusion(like the Join expression rework, the trait sets propagation, the
metadata etc.) And I felt very happy and respected to work with you guys in
the community. Let’s keep the good communications and output more valuable
design !

Thanks again to everyone !

Danny Chan
在 2019年10月22日 +0800 AM10:22,Julian Hyde <>,写道:
I agree that we’ve made good progress on last year’s big problem, pull
requests languishing for too long. The situation has been better, because a
few people are putting in considerable effort reviewing. We still have some
ways to go, so let’s keep up the good work.

One of the successes of the year was to arrange release managers for
several releases in advance. Each of the individuals stepped up and did a
great job, and the release process was as smooth as it could possibly be
for a project of this size. Because the work was shared, I think no
individual felt that they were taking on an undue burden.

I also want to mention the fact that we now have an awesome logo. Thank
you for pushing that change through!

+1 for Stamatis as candidate for the next PMC chair. I was going to
propose him also.

I am proud that we have appointed a new person as PMC chair every year.
Each chair has brought a new perspective and energy to the role, and has
advanced the community. Francis is no exception, and he has kept Calcite in
good shape. Thank you, Francis!

We were discussing in another thread about whether we should cleave
Avatica into a more separate sub-project or top-level project. But I do
note that Francis came from the Avatica side of the project (Avatica Go, in
fact) and yet effortlessly and effectively spoke for the whole Calcite
project. So, it gives me hope that there is still cohesion between the
Calcite and Avatica communities.


On Oct 20, 2019, at 6:50 PM, Danny Chan <> wrote:

Great work Francis! I’m + 1 for Stamatis being the PMC chair ~

Danny Chan
在 2019年10月21日 +0800 AM6:47,,写道:


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message