You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by Stamatis Zampetakis <za...@gmail.com> on 2020/01/01 10:18:55 UTC
Draft board report for January 2020
Attached below is a draft of this month's board report. I plan to submit it
on January 7. Please let me know if you have any additions or corrections.
## Description:
Apache Calcite is a highly customizable framework for parsing and planning
queries on data in a wide variety of formats. It allows database-like
access,
and in particular a SQL interface and advanced query optimization, for data
not
residing in a traditional database.
Avatica is a sub-project within Calcite and provides a framework for
building
local and remote JDBC and ODBC database drivers. Avatica has an independent
release schedule and its own repository.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Calcite was founded 2015-10-22 (4 years ago).
There are currently 45 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Danny Chen was added to the PMC on 2019-10-30.
- Haisheng Yuan was added to the PMC on 2019-11-11.
- Stamatis Zampetakis was appointed as PMC chair on 2019-12-18,
continuing the tradition of the project of rotating the chair every year.
- No new committers. Last addition was Mohamed Mohsen on 2019-09-17.
## Project Activity:
Calcite 1.21.0 was released in the middle of September, including more than
100
resolved issues and maintaining a release cadence of roughly one release per
quarter.
Calcite 1.22.0 is under preparation and is expected to be released inside
January while at the moment contains more than 230 commits and 150 resolved
issues.
Avatica 1.16.0 was released in the middle of December, including numerous
bug
fixes and security improvements while the build system has been migrated
from
maven to gradle.
The build and test infrastructure has been modernized for both Calcite and
Avatica, with the migration from maven to gradle, JUnit4 to JUnit5, and the
introduction of GitHub actions as part of the CI. The changes shall improve
developers experience, code quality, and protect better against
regressions.
Members of the project participated in ApacheCon EU on October and Flink
Forward
Asia on November, representing the community, and presenting talks about
Calcite.
Finally, the Hazelcast system has decided to adopt Calcite for query
planning.
## Community Health:
Activity levels on mailing lists (37%), git (40%) and JIRA (opened 15%,
closed
19%) have increased significantly in the last quarter. One reason is the
modernization of the build and test infrastructure for both Calcite and
Avatica,
which triggered many discussions and follow-up tasks. Another reason, is
the
changes in the roster of the PMC and open discussions about the future of
the
project. Last but not least, is the involvement of new people in the
community
bringing up new challenges and ideas for improvements.
The rates of pull requests being closed and merged on Github has increased
by
16%, as we work to clear our backlog. Nevertheless, the number of open pull
requests is still big since the number of committers who get involved in
reviews
is rather small. Furthermore, there are pull requests which are stale,
work in progress, or proposals that make the numbers look even bigger. On
the
positive side every pull request receives comments within a couple of days
after
being submitted and there are many which get merged without too much effort
showing that the project attracts skilled developers who may turn into
committers quite soon.
Re: Draft board report for January 2020
Posted by Stamatis Zampetakis <za...@gmail.com>.
Thanks everybody for the feedback, I submitted the report!
On Mon, Jan 6, 2020 at 9:17 PM Julian Hyde <jh...@apache.org> wrote:
> Is it worth mentioning that we have a new PMC chair? (Of course you’re too
> modest to mention it.)
>
> I am proud of the fact that we change the chair annually, and are now on
> our fifth (distinct) chair. Orderly transfer of power is a mark of a stable
> democracy.
>
> > On Jan 5, 2020, at 2:29 AM, Stamatis Zampetakis <za...@gmail.com>
> wrote:
> >
> > @Andrei: If I remember well both Ignite and Hazelcast decided to adopt
> > Calcite and we mentioned Ignite in the previous board report.
> >
> > Best,
> > Stamatis
> >
> > On Thu, Jan 2, 2020 at 9:49 PM Andrei Sereda <an...@sereda.cc> wrote:
> >
> >> +1
> >>
> >> Question regarding Hazelcast :
> >>
> >>> Finally, the Hazelcast system has decided to adopt Calcite for query
> >> planning.
> >>
> >> Was it Ignite [1] or Hazelcast team to adopt (prototype) Calcite ?
> >>
> >>
> >>
> https://lists.apache.org/thread.html/4211dbbe35690e70462370886afcbb35419ff016b0ee604acf07a4d3%40%3Cdev.ignite.apache.org%3E
> >> [1]
> >>
> >> On Thu, Jan 2, 2020 at 3:42 PM Rui Wang <am...@apache.org> wrote:
> >>
> >>> Looks nice! Thank you Stamatis!
> >>>
> >>>
> >>>
> >>> -Rui
> >>>
> >>>
> >>>
> >>> On Wed, Jan 1, 2020 at 6:52 PM Matt Wang <wa...@163.com> wrote:
> >>>
> >>>> +1, looks good. Thanks~
> >>>>
> >>>>
> >>>> ---
> >>>> Best,
> >>>> Matt Wang
> >>>>
> >>>>
> >>>> On 01/2/2020 09:57，Chunwei Lei<ch...@gmail.com> wrote：
> >>>> +1, looks good.
> >>>> Thanks, Stamatis~~
> >>>>
> >>>>
> >>>> Best,
> >>>> Chunwei
> >>>>
> >>>>
> >>>> On Thu, Jan 2, 2020 at 8:41 AM Haisheng Yuan <h....@alibaba-inc.com>
> >>>> wrote:
> >>>>
> >>>> +1, looks good to me.
> >>>> Thanks.
> >>>>
> >>>> - Haisheng
> >>>>
> >>>> ------------------------------------------------------------------
> >>>> 发件人：Francis Chuang<fr...@apache.org>
> >>>> 日 期：2020年01月02日 04:54:46
> >>>> 收件人：<de...@calcite.apache.org>
> >>>> 主 题：Re: Draft board report for January 2020
> >>>>
> >>>> +1, looks good, Stamatis!
> >>>>
> >>>> On 1/01/2020 9:18 pm, Stamatis Zampetakis wrote:
> >>>> Attached below is a draft of this month's board report. I plan to
> >> submit
> >>>> it
> >>>> on January 7. Please let me know if you have any additions or
> >>>> corrections.
> >>>>
> >>>> ## Description:
> >>>> Apache Calcite is a highly customizable framework for parsing and
> >>>> planning
> >>>> queries on data in a wide variety of formats. It allows database-like
> >>>> access,
> >>>> and in particular a SQL interface and advanced query optimization, for
> >>>> data
> >>>> not
> >>>> residing in a traditional database.
> >>>>
> >>>> Avatica is a sub-project within Calcite and provides a framework for
> >>>> building
> >>>> local and remote JDBC and ODBC database drivers. Avatica has an
> >>>> independent
> >>>> release schedule and its own repository.
> >>>>
> >>>> ## Issues:
> >>>> There are no issues requiring board attention.
> >>>>
> >>>> ## Membership Data:
> >>>> Apache Calcite was founded 2015-10-22 (4 years ago).
> >>>> There are currently 45 committers and 22 PMC members in this project.
> >>>> The Committer-to-PMC ratio is roughly 2:1.
> >>>>
> >>>> Community changes, past quarter:
> >>>> - Danny Chen was added to the PMC on 2019-10-30.
> >>>> - Haisheng Yuan was added to the PMC on 2019-11-11.
> >>>> - Stamatis Zampetakis was appointed as PMC chair on 2019-12-18,
> >>>> continuing the tradition of the project of rotating the chair every
> >> year.
> >>>> - No new committers. Last addition was Mohamed Mohsen on 2019-09-17.
> >>>>
> >>>> ## Project Activity:
> >>>> Calcite 1.21.0 was released in the middle of September, including more
> >>>> than
> >>>> 100
> >>>> resolved issues and maintaining a release cadence of roughly one
> >> release
> >>>> per
> >>>> quarter.
> >>>>
> >>>> Calcite 1.22.0 is under preparation and is expected to be released
> >> inside
> >>>> January while at the moment contains more than 230 commits and 150
> >>>> resolved
> >>>> issues.
> >>>>
> >>>> Avatica 1.16.0 was released in the middle of December, including
> >> numerous
> >>>> bug
> >>>> fixes and security improvements while the build system has been
> >> migrated
> >>>> from
> >>>> maven to gradle.
> >>>>
> >>>> The build and test infrastructure has been modernized for both Calcite
> >>>> and
> >>>> Avatica, with the migration from maven to gradle, JUnit4 to JUnit5,
> and
> >>>> the
> >>>> introduction of GitHub actions as part of the CI. The changes shall
> >>>> improve
> >>>> developers experience, code quality, and protect better against
> >>>> regressions.
> >>>>
> >>>> Members of the project participated in ApacheCon EU on October and
> >> Flink
> >>>> Forward
> >>>> Asia on November, representing the community, and presenting talks
> >> about
> >>>> Calcite.
> >>>>
> >>>> Finally, the Hazelcast system has decided to adopt Calcite for query
> >>>> planning.
> >>>>
> >>>> ## Community Health:
> >>>>
> >>>> Activity levels on mailing lists (37%), git (40%) and JIRA (opened
> 15%,
> >>>> closed
> >>>> 19%) have increased significantly in the last quarter. One reason is
> >> the
> >>>> modernization of the build and test infrastructure for both Calcite
> and
> >>>> Avatica,
> >>>> which triggered many discussions and follow-up tasks. Another reason,
> >> is
> >>>> the
> >>>> changes in the roster of the PMC and open discussions about the future
> >> of
> >>>> the
> >>>> project. Last but not least, is the involvement of new people in the
> >>>> community
> >>>> bringing up new challenges and ideas for improvements.
> >>>>
> >>>> The rates of pull requests being closed and merged on Github has
> >>>> increased
> >>>> by
> >>>> 16%, as we work to clear our backlog. Nevertheless, the number of open
> >>>> pull
> >>>> requests is still big since the number of committers who get involved
> >> in
> >>>> reviews
> >>>> is rather small. Furthermore, there are pull requests which are stale,
> >>>> work in progress, or proposals that make the numbers look even bigger.
> >> On
> >>>> the
> >>>> positive side every pull request receives comments within a couple of
> >>>> days
> >>>> after
> >>>> being submitted and there are many which get merged without too much
> >>>> effort
> >>>> showing that the project attracts skilled developers who may turn into
> >>>> committers quite soon.
> >>>>
> >>>>
> >>>>
> >>>
> >>
>
>
Re: Draft board report for January 2020
Posted by Juan Pan <pa...@apache.org>.
Totally agree. It deserves praise that rotate chair annually and run Calcite community so active and in order.
Juan Pan (Trista)
Senior DBA & PPMC of Apache ShardingSphere(Incubating)
E-mail: panjuan@apache.org
On 01/7/2020 04:17，Julian Hyde<jh...@apache.org> wrote：
Is it worth mentioning that we have a new PMC chair? (Of course you’re too modest to mention it.)
I am proud of the fact that we change the chair annually, and are now on our fifth (distinct) chair. Orderly transfer of power is a mark of a stable democracy.
On Jan 5, 2020, at 2:29 AM, Stamatis Zampetakis <za...@gmail.com> wrote:
@Andrei: If I remember well both Ignite and Hazelcast decided to adopt
Calcite and we mentioned Ignite in the previous board report.
Best,
Stamatis
On Thu, Jan 2, 2020 at 9:49 PM Andrei Sereda <an...@sereda.cc> wrote:
+1
Question regarding Hazelcast :
Finally, the Hazelcast system has decided to adopt Calcite for query
planning.
Was it Ignite [1] or Hazelcast team to adopt (prototype) Calcite ?
https://lists.apache.org/thread.html/4211dbbe35690e70462370886afcbb35419ff016b0ee604acf07a4d3%40%3Cdev.ignite.apache.org%3E
[1]
On Thu, Jan 2, 2020 at 3:42 PM Rui Wang <am...@apache.org> wrote:
Looks nice! Thank you Stamatis!
-Rui
On Wed, Jan 1, 2020 at 6:52 PM Matt Wang <wa...@163.com> wrote:
+1, looks good. Thanks~
---
Best,
Matt Wang
On 01/2/2020 09:57，Chunwei Lei<ch...@gmail.com> wrote：
+1, looks good.
Thanks, Stamatis~~
Best,
Chunwei
On Thu, Jan 2, 2020 at 8:41 AM Haisheng Yuan <h....@alibaba-inc.com>
wrote:
+1, looks good to me.
Thanks.
- Haisheng
------------------------------------------------------------------
发件人：Francis Chuang<fr...@apache.org>
日 期：2020年01月02日 04:54:46
收件人：<de...@calcite.apache.org>
主 题：Re: Draft board report for January 2020
+1, looks good, Stamatis!
On 1/01/2020 9:18 pm, Stamatis Zampetakis wrote:
Attached below is a draft of this month's board report. I plan to
submit
it
on January 7. Please let me know if you have any additions or
corrections.
## Description:
Apache Calcite is a highly customizable framework for parsing and
planning
queries on data in a wide variety of formats. It allows database-like
access,
and in particular a SQL interface and advanced query optimization, for
data
not
residing in a traditional database.
Avatica is a sub-project within Calcite and provides a framework for
building
local and remote JDBC and ODBC database drivers. Avatica has an
independent
release schedule and its own repository.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Calcite was founded 2015-10-22 (4 years ago).
There are currently 45 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Danny Chen was added to the PMC on 2019-10-30.
- Haisheng Yuan was added to the PMC on 2019-11-11.
- Stamatis Zampetakis was appointed as PMC chair on 2019-12-18,
continuing the tradition of the project of rotating the chair every
year.
- No new committers. Last addition was Mohamed Mohsen on 2019-09-17.
## Project Activity:
Calcite 1.21.0 was released in the middle of September, including more
than
100
resolved issues and maintaining a release cadence of roughly one
release
per
quarter.
Calcite 1.22.0 is under preparation and is expected to be released
inside
January while at the moment contains more than 230 commits and 150
resolved
issues.
Avatica 1.16.0 was released in the middle of December, including
numerous
bug
fixes and security improvements while the build system has been
migrated
from
maven to gradle.
The build and test infrastructure has been modernized for both Calcite
and
Avatica, with the migration from maven to gradle, JUnit4 to JUnit5, and
the
introduction of GitHub actions as part of the CI. The changes shall
improve
developers experience, code quality, and protect better against
regressions.
Members of the project participated in ApacheCon EU on October and
Flink
Forward
Asia on November, representing the community, and presenting talks
about
Calcite.
Finally, the Hazelcast system has decided to adopt Calcite for query
planning.
## Community Health:
Activity levels on mailing lists (37%), git (40%) and JIRA (opened 15%,
closed
19%) have increased significantly in the last quarter. One reason is
the
modernization of the build and test infrastructure for both Calcite and
Avatica,
which triggered many discussions and follow-up tasks. Another reason,
is
the
changes in the roster of the PMC and open discussions about the future
of
the
project. Last but not least, is the involvement of new people in the
community
bringing up new challenges and ideas for improvements.
The rates of pull requests being closed and merged on Github has
increased
by
16%, as we work to clear our backlog. Nevertheless, the number of open
pull
requests is still big since the number of committers who get involved
in
reviews
is rather small. Furthermore, there are pull requests which are stale,
work in progress, or proposals that make the numbers look even bigger.
On
the
positive side every pull request receives comments within a couple of
days
after
being submitted and there are many which get merged without too much
effort
showing that the project attracts skilled developers who may turn into
committers quite soon.
Re: Draft board report for January 2020
Posted by Julian Hyde <jh...@apache.org>.
Is it worth mentioning that we have a new PMC chair? (Of course you’re too modest to mention it.)
I am proud of the fact that we change the chair annually, and are now on our fifth (distinct) chair. Orderly transfer of power is a mark of a stable democracy.
> On Jan 5, 2020, at 2:29 AM, Stamatis Zampetakis <za...@gmail.com> wrote:
>
> @Andrei: If I remember well both Ignite and Hazelcast decided to adopt
> Calcite and we mentioned Ignite in the previous board report.
>
> Best,
> Stamatis
>
> On Thu, Jan 2, 2020 at 9:49 PM Andrei Sereda <an...@sereda.cc> wrote:
>
>> +1
>>
>> Question regarding Hazelcast :
>>
>>> Finally, the Hazelcast system has decided to adopt Calcite for query
>> planning.
>>
>> Was it Ignite [1] or Hazelcast team to adopt (prototype) Calcite ?
>>
>>
>> https://lists.apache.org/thread.html/4211dbbe35690e70462370886afcbb35419ff016b0ee604acf07a4d3%40%3Cdev.ignite.apache.org%3E
>> [1]
>>
>> On Thu, Jan 2, 2020 at 3:42 PM Rui Wang <am...@apache.org> wrote:
>>
>>> Looks nice! Thank you Stamatis!
>>>
>>>
>>>
>>> -Rui
>>>
>>>
>>>
>>> On Wed, Jan 1, 2020 at 6:52 PM Matt Wang <wa...@163.com> wrote:
>>>
>>>> +1, looks good. Thanks~
>>>>
>>>>
>>>> ---
>>>> Best,
>>>> Matt Wang
>>>>
>>>>
>>>> On 01/2/2020 09:57，Chunwei Lei<ch...@gmail.com> wrote：
>>>> +1, looks good.
>>>> Thanks, Stamatis~~
>>>>
>>>>
>>>> Best,
>>>> Chunwei
>>>>
>>>>
>>>> On Thu, Jan 2, 2020 at 8:41 AM Haisheng Yuan <h....@alibaba-inc.com>
>>>> wrote:
>>>>
>>>> +1, looks good to me.
>>>> Thanks.
>>>>
>>>> - Haisheng
>>>>
>>>> ------------------------------------------------------------------
>>>> 发件人：Francis Chuang<fr...@apache.org>
>>>> 日 期：2020年01月02日 04:54:46
>>>> 收件人：<de...@calcite.apache.org>
>>>> 主 题：Re: Draft board report for January 2020
>>>>
>>>> +1, looks good, Stamatis!
>>>>
>>>> On 1/01/2020 9:18 pm, Stamatis Zampetakis wrote:
>>>> Attached below is a draft of this month's board report. I plan to
>> submit
>>>> it
>>>> on January 7. Please let me know if you have any additions or
>>>> corrections.
>>>>
>>>> ## Description:
>>>> Apache Calcite is a highly customizable framework for parsing and
>>>> planning
>>>> queries on data in a wide variety of formats. It allows database-like
>>>> access,
>>>> and in particular a SQL interface and advanced query optimization, for
>>>> data
>>>> not
>>>> residing in a traditional database.
>>>>
>>>> Avatica is a sub-project within Calcite and provides a framework for
>>>> building
>>>> local and remote JDBC and ODBC database drivers. Avatica has an
>>>> independent
>>>> release schedule and its own repository.
>>>>
>>>> ## Issues:
>>>> There are no issues requiring board attention.
>>>>
>>>> ## Membership Data:
>>>> Apache Calcite was founded 2015-10-22 (4 years ago).
>>>> There are currently 45 committers and 22 PMC members in this project.
>>>> The Committer-to-PMC ratio is roughly 2:1.
>>>>
>>>> Community changes, past quarter:
>>>> - Danny Chen was added to the PMC on 2019-10-30.
>>>> - Haisheng Yuan was added to the PMC on 2019-11-11.
>>>> - Stamatis Zampetakis was appointed as PMC chair on 2019-12-18,
>>>> continuing the tradition of the project of rotating the chair every
>> year.
>>>> - No new committers. Last addition was Mohamed Mohsen on 2019-09-17.
>>>>
>>>> ## Project Activity:
>>>> Calcite 1.21.0 was released in the middle of September, including more
>>>> than
>>>> 100
>>>> resolved issues and maintaining a release cadence of roughly one
>> release
>>>> per
>>>> quarter.
>>>>
>>>> Calcite 1.22.0 is under preparation and is expected to be released
>> inside
>>>> January while at the moment contains more than 230 commits and 150
>>>> resolved
>>>> issues.
>>>>
>>>> Avatica 1.16.0 was released in the middle of December, including
>> numerous
>>>> bug
>>>> fixes and security improvements while the build system has been
>> migrated
>>>> from
>>>> maven to gradle.
>>>>
>>>> The build and test infrastructure has been modernized for both Calcite
>>>> and
>>>> Avatica, with the migration from maven to gradle, JUnit4 to JUnit5, and
>>>> the
>>>> introduction of GitHub actions as part of the CI. The changes shall
>>>> improve
>>>> developers experience, code quality, and protect better against
>>>> regressions.
>>>>
>>>> Members of the project participated in ApacheCon EU on October and
>> Flink
>>>> Forward
>>>> Asia on November, representing the community, and presenting talks
>> about
>>>> Calcite.
>>>>
>>>> Finally, the Hazelcast system has decided to adopt Calcite for query
>>>> planning.
>>>>
>>>> ## Community Health:
>>>>
>>>> Activity levels on mailing lists (37%), git (40%) and JIRA (opened 15%,
>>>> closed
>>>> 19%) have increased significantly in the last quarter. One reason is
>> the
>>>> modernization of the build and test infrastructure for both Calcite and
>>>> Avatica,
>>>> which triggered many discussions and follow-up tasks. Another reason,
>> is
>>>> the
>>>> changes in the roster of the PMC and open discussions about the future
>> of
>>>> the
>>>> project. Last but not least, is the involvement of new people in the
>>>> community
>>>> bringing up new challenges and ideas for improvements.
>>>>
>>>> The rates of pull requests being closed and merged on Github has
>>>> increased
>>>> by
>>>> 16%, as we work to clear our backlog. Nevertheless, the number of open
>>>> pull
>>>> requests is still big since the number of committers who get involved
>> in
>>>> reviews
>>>> is rather small. Furthermore, there are pull requests which are stale,
>>>> work in progress, or proposals that make the numbers look even bigger.
>> On
>>>> the
>>>> positive side every pull request receives comments within a couple of
>>>> days
>>>> after
>>>> being submitted and there are many which get merged without too much
>>>> effort
>>>> showing that the project attracts skilled developers who may turn into
>>>> committers quite soon.
>>>>
>>>>
>>>>
>>>
>>
Re: Draft board report for January 2020
Posted by Stamatis Zampetakis <za...@gmail.com>.
@Andrei: If I remember well both Ignite and Hazelcast decided to adopt
Calcite and we mentioned Ignite in the previous board report.
Best,
Stamatis
On Thu, Jan 2, 2020 at 9:49 PM Andrei Sereda <an...@sereda.cc> wrote:
> +1
>
> Question regarding Hazelcast :
>
> > Finally, the Hazelcast system has decided to adopt Calcite for query
> planning.
>
> Was it Ignite [1] or Hazelcast team to adopt (prototype) Calcite ?
>
>
> https://lists.apache.org/thread.html/4211dbbe35690e70462370886afcbb35419ff016b0ee604acf07a4d3%40%3Cdev.ignite.apache.org%3E
> [1]
>
> On Thu, Jan 2, 2020 at 3:42 PM Rui Wang <am...@apache.org> wrote:
>
> > Looks nice! Thank you Stamatis!
> >
> >
> >
> > -Rui
> >
> >
> >
> > On Wed, Jan 1, 2020 at 6:52 PM Matt Wang <wa...@163.com> wrote:
> >
> > > +1, looks good. Thanks~
> > >
> > >
> > > ---
> > > Best,
> > > Matt Wang
> > >
> > >
> > > On 01/2/2020 09:57，Chunwei Lei<ch...@gmail.com> wrote：
> > > +1, looks good.
> > > Thanks, Stamatis~~
> > >
> > >
> > > Best,
> > > Chunwei
> > >
> > >
> > > On Thu, Jan 2, 2020 at 8:41 AM Haisheng Yuan <h....@alibaba-inc.com>
> > > wrote:
> > >
> > > +1, looks good to me.
> > > Thanks.
> > >
> > > - Haisheng
> > >
> > > ------------------------------------------------------------------
> > > 发件人：Francis Chuang<fr...@apache.org>
> > > 日 期：2020年01月02日 04:54:46
> > > 收件人：<de...@calcite.apache.org>
> > > 主 题：Re: Draft board report for January 2020
> > >
> > > +1, looks good, Stamatis!
> > >
> > > On 1/01/2020 9:18 pm, Stamatis Zampetakis wrote:
> > > Attached below is a draft of this month's board report. I plan to
> submit
> > > it
> > > on January 7. Please let me know if you have any additions or
> > > corrections.
> > >
> > > ## Description:
> > > Apache Calcite is a highly customizable framework for parsing and
> > > planning
> > > queries on data in a wide variety of formats. It allows database-like
> > > access,
> > > and in particular a SQL interface and advanced query optimization, for
> > > data
> > > not
> > > residing in a traditional database.
> > >
> > > Avatica is a sub-project within Calcite and provides a framework for
> > > building
> > > local and remote JDBC and ODBC database drivers. Avatica has an
> > > independent
> > > release schedule and its own repository.
> > >
> > > ## Issues:
> > > There are no issues requiring board attention.
> > >
> > > ## Membership Data:
> > > Apache Calcite was founded 2015-10-22 (4 years ago).
> > > There are currently 45 committers and 22 PMC members in this project.
> > > The Committer-to-PMC ratio is roughly 2:1.
> > >
> > > Community changes, past quarter:
> > > - Danny Chen was added to the PMC on 2019-10-30.
> > > - Haisheng Yuan was added to the PMC on 2019-11-11.
> > > - Stamatis Zampetakis was appointed as PMC chair on 2019-12-18,
> > > continuing the tradition of the project of rotating the chair every
> year.
> > > - No new committers. Last addition was Mohamed Mohsen on 2019-09-17.
> > >
> > > ## Project Activity:
> > > Calcite 1.21.0 was released in the middle of September, including more
> > > than
> > > 100
> > > resolved issues and maintaining a release cadence of roughly one
> release
> > > per
> > > quarter.
> > >
> > > Calcite 1.22.0 is under preparation and is expected to be released
> inside
> > > January while at the moment contains more than 230 commits and 150
> > > resolved
> > > issues.
> > >
> > > Avatica 1.16.0 was released in the middle of December, including
> numerous
> > > bug
> > > fixes and security improvements while the build system has been
> migrated
> > > from
> > > maven to gradle.
> > >
> > > The build and test infrastructure has been modernized for both Calcite
> > > and
> > > Avatica, with the migration from maven to gradle, JUnit4 to JUnit5, and
> > > the
> > > introduction of GitHub actions as part of the CI. The changes shall
> > > improve
> > > developers experience, code quality, and protect better against
> > > regressions.
> > >
> > > Members of the project participated in ApacheCon EU on October and
> Flink
> > > Forward
> > > Asia on November, representing the community, and presenting talks
> about
> > > Calcite.
> > >
> > > Finally, the Hazelcast system has decided to adopt Calcite for query
> > > planning.
> > >
> > > ## Community Health:
> > >
> > > Activity levels on mailing lists (37%), git (40%) and JIRA (opened 15%,
> > > closed
> > > 19%) have increased significantly in the last quarter. One reason is
> the
> > > modernization of the build and test infrastructure for both Calcite and
> > > Avatica,
> > > which triggered many discussions and follow-up tasks. Another reason,
> is
> > > the
> > > changes in the roster of the PMC and open discussions about the future
> of
> > > the
> > > project. Last but not least, is the involvement of new people in the
> > > community
> > > bringing up new challenges and ideas for improvements.
> > >
> > > The rates of pull requests being closed and merged on Github has
> > > increased
> > > by
> > > 16%, as we work to clear our backlog. Nevertheless, the number of open
> > > pull
> > > requests is still big since the number of committers who get involved
> in
> > > reviews
> > > is rather small. Furthermore, there are pull requests which are stale,
> > > work in progress, or proposals that make the numbers look even bigger.
> On
> > > the
> > > positive side every pull request receives comments within a couple of
> > > days
> > > after
> > > being submitted and there are many which get merged without too much
> > > effort
> > > showing that the project attracts skilled developers who may turn into
> > > committers quite soon.
> > >
> > >
> > >
> >
>
Re: Draft board report for January 2020
Posted by Andrei Sereda <an...@sereda.cc>.
+1
Question regarding Hazelcast :
> Finally, the Hazelcast system has decided to adopt Calcite for query
planning.
Was it Ignite [1] or Hazelcast team to adopt (prototype) Calcite ?
https://lists.apache.org/thread.html/4211dbbe35690e70462370886afcbb35419ff016b0ee604acf07a4d3%40%3Cdev.ignite.apache.org%3E
[1]
On Thu, Jan 2, 2020 at 3:42 PM Rui Wang <am...@apache.org> wrote:
> Looks nice! Thank you Stamatis!
>
>
>
> -Rui
>
>
>
> On Wed, Jan 1, 2020 at 6:52 PM Matt Wang <wa...@163.com> wrote:
>
> > +1, looks good. Thanks~
> >
> >
> > ---
> > Best,
> > Matt Wang
> >
> >
> > On 01/2/2020 09:57，Chunwei Lei<ch...@gmail.com> wrote：
> > +1, looks good.
> > Thanks, Stamatis~~
> >
> >
> > Best,
> > Chunwei
> >
> >
> > On Thu, Jan 2, 2020 at 8:41 AM Haisheng Yuan <h....@alibaba-inc.com>
> > wrote:
> >
> > +1, looks good to me.
> > Thanks.
> >
> > - Haisheng
> >
> > ------------------------------------------------------------------
> > 发件人：Francis Chuang<fr...@apache.org>
> > 日 期：2020年01月02日 04:54:46
> > 收件人：<de...@calcite.apache.org>
> > 主 题：Re: Draft board report for January 2020
> >
> > +1, looks good, Stamatis!
> >
> > On 1/01/2020 9:18 pm, Stamatis Zampetakis wrote:
> > Attached below is a draft of this month's board report. I plan to submit
> > it
> > on January 7. Please let me know if you have any additions or
> > corrections.
> >
> > ## Description:
> > Apache Calcite is a highly customizable framework for parsing and
> > planning
> > queries on data in a wide variety of formats. It allows database-like
> > access,
> > and in particular a SQL interface and advanced query optimization, for
> > data
> > not
> > residing in a traditional database.
> >
> > Avatica is a sub-project within Calcite and provides a framework for
> > building
> > local and remote JDBC and ODBC database drivers. Avatica has an
> > independent
> > release schedule and its own repository.
> >
> > ## Issues:
> > There are no issues requiring board attention.
> >
> > ## Membership Data:
> > Apache Calcite was founded 2015-10-22 (4 years ago).
> > There are currently 45 committers and 22 PMC members in this project.
> > The Committer-to-PMC ratio is roughly 2:1.
> >
> > Community changes, past quarter:
> > - Danny Chen was added to the PMC on 2019-10-30.
> > - Haisheng Yuan was added to the PMC on 2019-11-11.
> > - Stamatis Zampetakis was appointed as PMC chair on 2019-12-18,
> > continuing the tradition of the project of rotating the chair every year.
> > - No new committers. Last addition was Mohamed Mohsen on 2019-09-17.
> >
> > ## Project Activity:
> > Calcite 1.21.0 was released in the middle of September, including more
> > than
> > 100
> > resolved issues and maintaining a release cadence of roughly one release
> > per
> > quarter.
> >
> > Calcite 1.22.0 is under preparation and is expected to be released inside
> > January while at the moment contains more than 230 commits and 150
> > resolved
> > issues.
> >
> > Avatica 1.16.0 was released in the middle of December, including numerous
> > bug
> > fixes and security improvements while the build system has been migrated
> > from
> > maven to gradle.
> >
> > The build and test infrastructure has been modernized for both Calcite
> > and
> > Avatica, with the migration from maven to gradle, JUnit4 to JUnit5, and
> > the
> > introduction of GitHub actions as part of the CI. The changes shall
> > improve
> > developers experience, code quality, and protect better against
> > regressions.
> >
> > Members of the project participated in ApacheCon EU on October and Flink
> > Forward
> > Asia on November, representing the community, and presenting talks about
> > Calcite.
> >
> > Finally, the Hazelcast system has decided to adopt Calcite for query
> > planning.
> >
> > ## Community Health:
> >
> > Activity levels on mailing lists (37%), git (40%) and JIRA (opened 15%,
> > closed
> > 19%) have increased significantly in the last quarter. One reason is the
> > modernization of the build and test infrastructure for both Calcite and
> > Avatica,
> > which triggered many discussions and follow-up tasks. Another reason, is
> > the
> > changes in the roster of the PMC and open discussions about the future of
> > the
> > project. Last but not least, is the involvement of new people in the
> > community
> > bringing up new challenges and ideas for improvements.
> >
> > The rates of pull requests being closed and merged on Github has
> > increased
> > by
> > 16%, as we work to clear our backlog. Nevertheless, the number of open
> > pull
> > requests is still big since the number of committers who get involved in
> > reviews
> > is rather small. Furthermore, there are pull requests which are stale,
> > work in progress, or proposals that make the numbers look even bigger. On
> > the
> > positive side every pull request receives comments within a couple of
> > days
> > after
> > being submitted and there are many which get merged without too much
> > effort
> > showing that the project attracts skilled developers who may turn into
> > committers quite soon.
> >
> >
> >
>
Re: Draft board report for January 2020
Posted by Rui Wang <am...@apache.org>.
Looks nice! Thank you Stamatis!
-Rui
On Wed, Jan 1, 2020 at 6:52 PM Matt Wang <wa...@163.com> wrote:
> +1, looks good. Thanks~
>
>
> ---
> Best,
> Matt Wang
>
>
> On 01/2/2020 09:57，Chunwei Lei<ch...@gmail.com> wrote：
> +1, looks good.
> Thanks, Stamatis~~
>
>
> Best,
> Chunwei
>
>
> On Thu, Jan 2, 2020 at 8:41 AM Haisheng Yuan <h....@alibaba-inc.com>
> wrote:
>
> +1, looks good to me.
> Thanks.
>
> - Haisheng
>
> ------------------------------------------------------------------
> 发件人：Francis Chuang<fr...@apache.org>
> 日 期：2020年01月02日 04:54:46
> 收件人：<de...@calcite.apache.org>
> 主 题：Re: Draft board report for January 2020
>
> +1, looks good, Stamatis!
>
> On 1/01/2020 9:18 pm, Stamatis Zampetakis wrote:
> Attached below is a draft of this month's board report. I plan to submit
> it
> on January 7. Please let me know if you have any additions or
> corrections.
>
> ## Description:
> Apache Calcite is a highly customizable framework for parsing and
> planning
> queries on data in a wide variety of formats. It allows database-like
> access,
> and in particular a SQL interface and advanced query optimization, for
> data
> not
> residing in a traditional database.
>
> Avatica is a sub-project within Calcite and provides a framework for
> building
> local and remote JDBC and ODBC database drivers. Avatica has an
> independent
> release schedule and its own repository.
>
> ## Issues:
> There are no issues requiring board attention.
>
> ## Membership Data:
> Apache Calcite was founded 2015-10-22 (4 years ago).
> There are currently 45 committers and 22 PMC members in this project.
> The Committer-to-PMC ratio is roughly 2:1.
>
> Community changes, past quarter:
> - Danny Chen was added to the PMC on 2019-10-30.
> - Haisheng Yuan was added to the PMC on 2019-11-11.
> - Stamatis Zampetakis was appointed as PMC chair on 2019-12-18,
> continuing the tradition of the project of rotating the chair every year.
> - No new committers. Last addition was Mohamed Mohsen on 2019-09-17.
>
> ## Project Activity:
> Calcite 1.21.0 was released in the middle of September, including more
> than
> 100
> resolved issues and maintaining a release cadence of roughly one release
> per
> quarter.
>
> Calcite 1.22.0 is under preparation and is expected to be released inside
> January while at the moment contains more than 230 commits and 150
> resolved
> issues.
>
> Avatica 1.16.0 was released in the middle of December, including numerous
> bug
> fixes and security improvements while the build system has been migrated
> from
> maven to gradle.
>
> The build and test infrastructure has been modernized for both Calcite
> and
> Avatica, with the migration from maven to gradle, JUnit4 to JUnit5, and
> the
> introduction of GitHub actions as part of the CI. The changes shall
> improve
> developers experience, code quality, and protect better against
> regressions.
>
> Members of the project participated in ApacheCon EU on October and Flink
> Forward
> Asia on November, representing the community, and presenting talks about
> Calcite.
>
> Finally, the Hazelcast system has decided to adopt Calcite for query
> planning.
>
> ## Community Health:
>
> Activity levels on mailing lists (37%), git (40%) and JIRA (opened 15%,
> closed
> 19%) have increased significantly in the last quarter. One reason is the
> modernization of the build and test infrastructure for both Calcite and
> Avatica,
> which triggered many discussions and follow-up tasks. Another reason, is
> the
> changes in the roster of the PMC and open discussions about the future of
> the
> project. Last but not least, is the involvement of new people in the
> community
> bringing up new challenges and ideas for improvements.
>
> The rates of pull requests being closed and merged on Github has
> increased
> by
> 16%, as we work to clear our backlog. Nevertheless, the number of open
> pull
> requests is still big since the number of committers who get involved in
> reviews
> is rather small. Furthermore, there are pull requests which are stale,
> work in progress, or proposals that make the numbers look even bigger. On
> the
> positive side every pull request receives comments within a couple of
> days
> after
> being submitted and there are many which get merged without too much
> effort
> showing that the project attracts skilled developers who may turn into
> committers quite soon.
>
>
>
Re: Draft board report for January 2020
Posted by Matt Wang <wa...@163.com>.
+1, looks good. Thanks~
---
Best,
Matt Wang
On 01/2/2020 09:57，Chunwei Lei<ch...@gmail.com> wrote：
+1, looks good.
Thanks, Stamatis~~
Best,
Chunwei
On Thu, Jan 2, 2020 at 8:41 AM Haisheng Yuan <h....@alibaba-inc.com> wrote:
+1, looks good to me.
Thanks.
- Haisheng
------------------------------------------------------------------
发件人：Francis Chuang<fr...@apache.org>
日 期：2020年01月02日 04:54:46
收件人：<de...@calcite.apache.org>
主 题：Re: Draft board report for January 2020
+1, looks good, Stamatis!
On 1/01/2020 9:18 pm, Stamatis Zampetakis wrote:
Attached below is a draft of this month's board report. I plan to submit
it
on January 7. Please let me know if you have any additions or
corrections.
## Description:
Apache Calcite is a highly customizable framework for parsing and
planning
queries on data in a wide variety of formats. It allows database-like
access,
and in particular a SQL interface and advanced query optimization, for
data
not
residing in a traditional database.
Avatica is a sub-project within Calcite and provides a framework for
building
local and remote JDBC and ODBC database drivers. Avatica has an
independent
release schedule and its own repository.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Calcite was founded 2015-10-22 (4 years ago).
There are currently 45 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Danny Chen was added to the PMC on 2019-10-30.
- Haisheng Yuan was added to the PMC on 2019-11-11.
- Stamatis Zampetakis was appointed as PMC chair on 2019-12-18,
continuing the tradition of the project of rotating the chair every year.
- No new committers. Last addition was Mohamed Mohsen on 2019-09-17.
## Project Activity:
Calcite 1.21.0 was released in the middle of September, including more
than
100
resolved issues and maintaining a release cadence of roughly one release
per
quarter.
Calcite 1.22.0 is under preparation and is expected to be released inside
January while at the moment contains more than 230 commits and 150
resolved
issues.
Avatica 1.16.0 was released in the middle of December, including numerous
bug
fixes and security improvements while the build system has been migrated
from
maven to gradle.
The build and test infrastructure has been modernized for both Calcite
and
Avatica, with the migration from maven to gradle, JUnit4 to JUnit5, and
the
introduction of GitHub actions as part of the CI. The changes shall
improve
developers experience, code quality, and protect better against
regressions.
Members of the project participated in ApacheCon EU on October and Flink
Forward
Asia on November, representing the community, and presenting talks about
Calcite.
Finally, the Hazelcast system has decided to adopt Calcite for query
planning.
## Community Health:
Activity levels on mailing lists (37%), git (40%) and JIRA (opened 15%,
closed
19%) have increased significantly in the last quarter. One reason is the
modernization of the build and test infrastructure for both Calcite and
Avatica,
which triggered many discussions and follow-up tasks. Another reason, is
the
changes in the roster of the PMC and open discussions about the future of
the
project. Last but not least, is the involvement of new people in the
community
bringing up new challenges and ideas for improvements.
The rates of pull requests being closed and merged on Github has
increased
by
16%, as we work to clear our backlog. Nevertheless, the number of open
pull
requests is still big since the number of committers who get involved in
reviews
is rather small. Furthermore, there are pull requests which are stale,
work in progress, or proposals that make the numbers look even bigger. On
the
positive side every pull request receives comments within a couple of
days
after
being submitted and there are many which get merged without too much
effort
showing that the project attracts skilled developers who may turn into
committers quite soon.
Re: Re: Draft board report for January 2020
Posted by Chunwei Lei <ch...@gmail.com>.
+1, looks good.
Thanks, Stamatis~~
Best,
Chunwei
On Thu, Jan 2, 2020 at 8:41 AM Haisheng Yuan <h....@alibaba-inc.com> wrote:
> +1, looks good to me.
> Thanks.
>
> - Haisheng
>
> ------------------------------------------------------------------
> 发件人：Francis Chuang<fr...@apache.org>
> 日 期：2020年01月02日 04:54:46
> 收件人：<de...@calcite.apache.org>
> 主 题：Re: Draft board report for January 2020
>
> +1, looks good, Stamatis!
>
> On 1/01/2020 9:18 pm, Stamatis Zampetakis wrote:
> > Attached below is a draft of this month's board report. I plan to submit
> it
> > on January 7. Please let me know if you have any additions or
> corrections.
> >
> > ## Description:
> > Apache Calcite is a highly customizable framework for parsing and
> planning
> > queries on data in a wide variety of formats. It allows database-like
> > access,
> > and in particular a SQL interface and advanced query optimization, for
> data
> > not
> > residing in a traditional database.
> >
> > Avatica is a sub-project within Calcite and provides a framework for
> > building
> > local and remote JDBC and ODBC database drivers. Avatica has an
> independent
> > release schedule and its own repository.
> >
> > ## Issues:
> > There are no issues requiring board attention.
> >
> > ## Membership Data:
> > Apache Calcite was founded 2015-10-22 (4 years ago).
> > There are currently 45 committers and 22 PMC members in this project.
> > The Committer-to-PMC ratio is roughly 2:1.
> >
> > Community changes, past quarter:
> > - Danny Chen was added to the PMC on 2019-10-30.
> > - Haisheng Yuan was added to the PMC on 2019-11-11.
> > - Stamatis Zampetakis was appointed as PMC chair on 2019-12-18,
> > continuing the tradition of the project of rotating the chair every year.
> > - No new committers. Last addition was Mohamed Mohsen on 2019-09-17.
> >
> > ## Project Activity:
> > Calcite 1.21.0 was released in the middle of September, including more
> than
> > 100
> > resolved issues and maintaining a release cadence of roughly one release
> per
> > quarter.
> >
> > Calcite 1.22.0 is under preparation and is expected to be released inside
> > January while at the moment contains more than 230 commits and 150
> resolved
> > issues.
> >
> > Avatica 1.16.0 was released in the middle of December, including numerous
> > bug
> > fixes and security improvements while the build system has been migrated
> > from
> > maven to gradle.
> >
> > The build and test infrastructure has been modernized for both Calcite
> and
> > Avatica, with the migration from maven to gradle, JUnit4 to JUnit5, and
> the
> > introduction of GitHub actions as part of the CI. The changes shall
> improve
> > developers experience, code quality, and protect better against
> > regressions.
> >
> > Members of the project participated in ApacheCon EU on October and Flink
> > Forward
> > Asia on November, representing the community, and presenting talks about
> > Calcite.
> >
> > Finally, the Hazelcast system has decided to adopt Calcite for query
> > planning.
> >
> > ## Community Health:
> >
> > Activity levels on mailing lists (37%), git (40%) and JIRA (opened 15%,
> > closed
> > 19%) have increased significantly in the last quarter. One reason is the
> > modernization of the build and test infrastructure for both Calcite and
> > Avatica,
> > which triggered many discussions and follow-up tasks. Another reason, is
> > the
> > changes in the roster of the PMC and open discussions about the future of
> > the
> > project. Last but not least, is the involvement of new people in the
> > community
> > bringing up new challenges and ideas for improvements.
> >
> > The rates of pull requests being closed and merged on Github has
> increased
> > by
> > 16%, as we work to clear our backlog. Nevertheless, the number of open
> pull
> > requests is still big since the number of committers who get involved in
> > reviews
> > is rather small. Furthermore, there are pull requests which are stale,
> > work in progress, or proposals that make the numbers look even bigger. On
> > the
> > positive side every pull request receives comments within a couple of
> days
> > after
> > being submitted and there are many which get merged without too much
> effort
> > showing that the project attracts skilled developers who may turn into
> > committers quite soon.
> >
>
Re: Re: Draft board report for January 2020
Posted by Haisheng Yuan <h....@alibaba-inc.com>.
+1, looks good to me.
Thanks.
- Haisheng
------------------------------------------------------------------
发件人：Francis Chuang<fr...@apache.org>
日 期：2020年01月02日 04:54:46
收件人：<de...@calcite.apache.org>
主 题：Re: Draft board report for January 2020
+1, looks good, Stamatis!
On 1/01/2020 9:18 pm, Stamatis Zampetakis wrote:
> Attached below is a draft of this month's board report. I plan to submit it
> on January 7. Please let me know if you have any additions or corrections.
>
> ## Description:
> Apache Calcite is a highly customizable framework for parsing and planning
> queries on data in a wide variety of formats. It allows database-like
> access,
> and in particular a SQL interface and advanced query optimization, for data
> not
> residing in a traditional database.
>
> Avatica is a sub-project within Calcite and provides a framework for
> building
> local and remote JDBC and ODBC database drivers. Avatica has an independent
> release schedule and its own repository.
>
> ## Issues:
> There are no issues requiring board attention.
>
> ## Membership Data:
> Apache Calcite was founded 2015-10-22 (4 years ago).
> There are currently 45 committers and 22 PMC members in this project.
> The Committer-to-PMC ratio is roughly 2:1.
>
> Community changes, past quarter:
> - Danny Chen was added to the PMC on 2019-10-30.
> - Haisheng Yuan was added to the PMC on 2019-11-11.
> - Stamatis Zampetakis was appointed as PMC chair on 2019-12-18,
> continuing the tradition of the project of rotating the chair every year.
> - No new committers. Last addition was Mohamed Mohsen on 2019-09-17.
>
> ## Project Activity:
> Calcite 1.21.0 was released in the middle of September, including more than
> 100
> resolved issues and maintaining a release cadence of roughly one release per
> quarter.
>
> Calcite 1.22.0 is under preparation and is expected to be released inside
> January while at the moment contains more than 230 commits and 150 resolved
> issues.
>
> Avatica 1.16.0 was released in the middle of December, including numerous
> bug
> fixes and security improvements while the build system has been migrated
> from
> maven to gradle.
>
> The build and test infrastructure has been modernized for both Calcite and
> Avatica, with the migration from maven to gradle, JUnit4 to JUnit5, and the
> introduction of GitHub actions as part of the CI. The changes shall improve
> developers experience, code quality, and protect better against
> regressions.
>
> Members of the project participated in ApacheCon EU on October and Flink
> Forward
> Asia on November, representing the community, and presenting talks about
> Calcite.
>
> Finally, the Hazelcast system has decided to adopt Calcite for query
> planning.
>
> ## Community Health:
>
> Activity levels on mailing lists (37%), git (40%) and JIRA (opened 15%,
> closed
> 19%) have increased significantly in the last quarter. One reason is the
> modernization of the build and test infrastructure for both Calcite and
> Avatica,
> which triggered many discussions and follow-up tasks. Another reason, is
> the
> changes in the roster of the PMC and open discussions about the future of
> the
> project. Last but not least, is the involvement of new people in the
> community
> bringing up new challenges and ideas for improvements.
>
> The rates of pull requests being closed and merged on Github has increased
> by
> 16%, as we work to clear our backlog. Nevertheless, the number of open pull
> requests is still big since the number of committers who get involved in
> reviews
> is rather small. Furthermore, there are pull requests which are stale,
> work in progress, or proposals that make the numbers look even bigger. On
> the
> positive side every pull request receives comments within a couple of days
> after
> being submitted and there are many which get merged without too much effort
> showing that the project attracts skilled developers who may turn into
> committers quite soon.
>
Re: Draft board report for January 2020
Posted by Francis Chuang <fr...@apache.org>.
+1, looks good, Stamatis!
On 1/01/2020 9:18 pm, Stamatis Zampetakis wrote:
> Attached below is a draft of this month's board report. I plan to submit it
> on January 7. Please let me know if you have any additions or corrections.
>
> ## Description:
> Apache Calcite is a highly customizable framework for parsing and planning
> queries on data in a wide variety of formats. It allows database-like
> access,
> and in particular a SQL interface and advanced query optimization, for data
> not
> residing in a traditional database.
>
> Avatica is a sub-project within Calcite and provides a framework for
> building
> local and remote JDBC and ODBC database drivers. Avatica has an independent
> release schedule and its own repository.
>
> ## Issues:
> There are no issues requiring board attention.
>
> ## Membership Data:
> Apache Calcite was founded 2015-10-22 (4 years ago).
> There are currently 45 committers and 22 PMC members in this project.
> The Committer-to-PMC ratio is roughly 2:1.
>
> Community changes, past quarter:
> - Danny Chen was added to the PMC on 2019-10-30.
> - Haisheng Yuan was added to the PMC on 2019-11-11.
> - Stamatis Zampetakis was appointed as PMC chair on 2019-12-18,
> continuing the tradition of the project of rotating the chair every year.
> - No new committers. Last addition was Mohamed Mohsen on 2019-09-17.
>
> ## Project Activity:
> Calcite 1.21.0 was released in the middle of September, including more than
> 100
> resolved issues and maintaining a release cadence of roughly one release per
> quarter.
>
> Calcite 1.22.0 is under preparation and is expected to be released inside
> January while at the moment contains more than 230 commits and 150 resolved
> issues.
>
> Avatica 1.16.0 was released in the middle of December, including numerous
> bug
> fixes and security improvements while the build system has been migrated
> from
> maven to gradle.
>
> The build and test infrastructure has been modernized for both Calcite and
> Avatica, with the migration from maven to gradle, JUnit4 to JUnit5, and the
> introduction of GitHub actions as part of the CI. The changes shall improve
> developers experience, code quality, and protect better against
> regressions.
>
> Members of the project participated in ApacheCon EU on October and Flink
> Forward
> Asia on November, representing the community, and presenting talks about
> Calcite.
>
> Finally, the Hazelcast system has decided to adopt Calcite for query
> planning.
>
> ## Community Health:
>
> Activity levels on mailing lists (37%), git (40%) and JIRA (opened 15%,
> closed
> 19%) have increased significantly in the last quarter. One reason is the
> modernization of the build and test infrastructure for both Calcite and
> Avatica,
> which triggered many discussions and follow-up tasks. Another reason, is
> the
> changes in the roster of the PMC and open discussions about the future of
> the
> project. Last but not least, is the involvement of new people in the
> community
> bringing up new challenges and ideas for improvements.
>
> The rates of pull requests being closed and merged on Github has increased
> by
> 16%, as we work to clear our backlog. Nevertheless, the number of open pull
> requests is still big since the number of committers who get involved in
> reviews
> is rather small. Furthermore, there are pull requests which are stale,
> work in progress, or proposals that make the numbers look even bigger. On
> the
> positive side every pull request receives comments within a couple of days
> after
> being submitted and there are many which get merged without too much effort
> showing that the project attracts skilled developers who may turn into
> committers quite soon.
>
Re: Draft board report for January 2020
Posted by Michael Mior <mm...@apache.org>.
Looks good to me! Thanks Stamatis :)
--
Michael Mior
mmior@apache.org
Le mer. 1 janv. 2020 à 05:19, Stamatis Zampetakis <za...@gmail.com> a écrit :
>
> Attached below is a draft of this month's board report. I plan to submit it
> on January 7. Please let me know if you have any additions or corrections.
>
> ## Description:
> Apache Calcite is a highly customizable framework for parsing and planning
> queries on data in a wide variety of formats. It allows database-like
> access,
> and in particular a SQL interface and advanced query optimization, for data
> not
> residing in a traditional database.
>
> Avatica is a sub-project within Calcite and provides a framework for
> building
> local and remote JDBC and ODBC database drivers. Avatica has an independent
> release schedule and its own repository.
>
> ## Issues:
> There are no issues requiring board attention.
>
> ## Membership Data:
> Apache Calcite was founded 2015-10-22 (4 years ago).
> There are currently 45 committers and 22 PMC members in this project.
> The Committer-to-PMC ratio is roughly 2:1.
>
> Community changes, past quarter:
> - Danny Chen was added to the PMC on 2019-10-30.
> - Haisheng Yuan was added to the PMC on 2019-11-11.
> - Stamatis Zampetakis was appointed as PMC chair on 2019-12-18,
> continuing the tradition of the project of rotating the chair every year.
> - No new committers. Last addition was Mohamed Mohsen on 2019-09-17.
>
> ## Project Activity:
> Calcite 1.21.0 was released in the middle of September, including more than
> 100
> resolved issues and maintaining a release cadence of roughly one release per
> quarter.
>
> Calcite 1.22.0 is under preparation and is expected to be released inside
> January while at the moment contains more than 230 commits and 150 resolved
> issues.
>
> Avatica 1.16.0 was released in the middle of December, including numerous
> bug
> fixes and security improvements while the build system has been migrated
> from
> maven to gradle.
>
> The build and test infrastructure has been modernized for both Calcite and
> Avatica, with the migration from maven to gradle, JUnit4 to JUnit5, and the
> introduction of GitHub actions as part of the CI. The changes shall improve
> developers experience, code quality, and protect better against
> regressions.
>
> Members of the project participated in ApacheCon EU on October and Flink
> Forward
> Asia on November, representing the community, and presenting talks about
> Calcite.
>
> Finally, the Hazelcast system has decided to adopt Calcite for query
> planning.
>
> ## Community Health:
>
> Activity levels on mailing lists (37%), git (40%) and JIRA (opened 15%,
> closed
> 19%) have increased significantly in the last quarter. One reason is the
> modernization of the build and test infrastructure for both Calcite and
> Avatica,
> which triggered many discussions and follow-up tasks. Another reason, is
> the
> changes in the roster of the PMC and open discussions about the future of
> the
> project. Last but not least, is the involvement of new people in the
> community
> bringing up new challenges and ideas for improvements.
>
> The rates of pull requests being closed and merged on Github has increased
> by
> 16%, as we work to clear our backlog. Nevertheless, the number of open pull
> requests is still big since the number of committers who get involved in
> reviews
> is rather small. Furthermore, there are pull requests which are stale,
> work in progress, or proposals that make the numbers look even bigger. On
> the
> positive side every pull request receives comments within a couple of days
> after
> being submitted and there are many which get merged without too much effort
> showing that the project attracts skilled developers who may turn into
> committers quite soon.
Re: [DISCUSS] Why ProjectRemoveRule dose not consider field name when
apply this rule
Posted by Rui Wang <am...@apache.org>.
Sorry, I meant "I am not sure if Calcite does it" (likely not).
-Rui
On Wed, May 27, 2020 at 10:31 AM Rui Wang <am...@apache.org> wrote:
> Hello,
>
> This topic was discussed in
> https://issues.apache.org/jira/browse/CALCITE-1584.
>
> I am sure if Calcite does it, but in another SQL parser/analyzer
> implementation I have saw, each logical plan has a top attribute about
> final output column names, so even nodes might be merged/removed, at least
> there are still output column names that we can get.
>
> -Rui
>
> On Wed, May 27, 2020 at 5:38 AM 董 一峰 <do...@outlook.com> wrote:
>
>> Hello everyone,
>>
>> When we run the following test case:
>> SQL:
>> WITH T_CTE (i1_cte, i2_cte) AS (
>> SELECT
>> i1,
>> d3
>> FROM
>> t1
>> )
>> SELECT
>> *
>> FROM
>> t2
>> JOIN T_CTE ON (t2.i1 = T_CTE.i1_cte)
>>
>>
>> Logical Plan(After ProjectRemoveRule):
>> LogicalJoin(condition=[=($0, $14)], joinType=[inner])
>> :- LogicalTableScan(table=[[default, db1, t2]])
>> +- LogicalCalc(expr#0..13=[{inputs}], i1=[$t0], d3=[$t2])
>> +- LogicalTableScan(table=[[default, db1, t1]])
>>
>>
>> We wish the output column name contain i1_cte, i2_cte, but calcite just
>> drop it.
>> After analysisinp the calcite code, we found the rule named
>> ProjectRemoveRule, it will remove the project if project and its input has
>> same size and type, but it confused me, why this rule dose not consider the
>> field name when remove project?
>>
>> Best Regards
>> Axis
>>
>>
Re: [DISCUSS] Why ProjectRemoveRule dose not consider field name when
apply this rule
Posted by Rui Wang <am...@apache.org>.
Hello,
This topic was discussed in
https://issues.apache.org/jira/browse/CALCITE-1584.
I am sure if Calcite does it, but in another SQL parser/analyzer
implementation I have saw, each logical plan has a top attribute about
final output column names, so even nodes might be merged/removed, at least
there are still output column names that we can get.
-Rui
On Wed, May 27, 2020 at 5:38 AM 董 一峰 <do...@outlook.com> wrote:
> Hello everyone,
>
> When we run the following test case:
> SQL:
> WITH T_CTE (i1_cte, i2_cte) AS (
> SELECT
> i1,
> d3
> FROM
> t1
> )
> SELECT
> *
> FROM
> t2
> JOIN T_CTE ON (t2.i1 = T_CTE.i1_cte)
>
>
> Logical Plan(After ProjectRemoveRule):
> LogicalJoin(condition=[=($0, $14)], joinType=[inner])
> :- LogicalTableScan(table=[[default, db1, t2]])
> +- LogicalCalc(expr#0..13=[{inputs}], i1=[$t0], d3=[$t2])
> +- LogicalTableScan(table=[[default, db1, t1]])
>
>
> We wish the output column name contain i1_cte, i2_cte, but calcite just
> drop it.
> After analysisinp the calcite code, we found the rule named
> ProjectRemoveRule, it will remove the project if project and its input has
> same size and type, but it confused me, why this rule dose not consider the
> field name when remove project?
>
> Best Regards
> Axis
>
>
[DISCUSS] Why ProjectRemoveRule dose not consider field name
when apply this rule
Posted by 董 一峰 <do...@outlook.com>.
Hello everyone,
When we run the following test case:
SQL:
WITH T_CTE (i1_cte, i2_cte) AS (
SELECT
i1,
d3
FROM
t1
)
SELECT
*
FROM
t2
JOIN T_CTE ON (t2.i1 = T_CTE.i1_cte)
Logical Plan(After ProjectRemoveRule):
LogicalJoin(condition=[=($0, $14)], joinType=[inner])
:- LogicalTableScan(table=[[default, db1, t2]])
+- LogicalCalc(expr#0..13=[{inputs}], i1=[$t0], d3=[$t2])
+- LogicalTableScan(table=[[default, db1, t1]])
We wish the output column name contain i1_cte, i2_cte, but calcite just drop it.
After analysisinp the calcite code, we found the rule named ProjectRemoveRule, it will remove the project if project and its input has same size and type, but it confused me, why this rule dose not consider the field name when remove project?
Best Regards
Axis