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/10/05 22:04:06 UTC
Draft board report for October 2020
Attached below is a draft of this month's board report. I plan to submit it
on October 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:
There are currently 51 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- Ruben Quesada Lopez was added to the PMC on 2020-08-10
- Rui Wang was added as committer on 2020-09-07
## Project Activity:
Avatica Go 5.0.0 was released on 2020-07-16. It is a major release of
Avatica
Go with a number of improvements and a breaking change affecting connection
metadata. Worth mentioning the support for batching query string parameters
in
the DSN, allowing updates to the server to be executed once Close() is
called
on the prepared statement.
Calcite 1.24.0 was released on 2020-07-24, including more than 80 resolved
issues. Among those it’s worth highlighting some new features of the
optimizer
for more efficient search space pruning as well as the support of a new SQL
dialect for Presto.
Calcite 1.25.0 was released on 2020-08-22, with fewer but important features
improving the parameterization of optimizer rules, adding support for new
spatial functions, and interval expressions. The release also introduced a
few
breaking changes but so far the users seem to have embraced the changes.
Members of the community gave talks at ApacheCon 2020, bringing to the
surface
Calcite through discussions about other projects. Although we didn’t have
talks dedicated to Calcite, it is nice to receive mentions and witness the
adoption of Calcite by other open source projects and people in Academia.
## Community Health:
The overall activity in the community has slightly decreased in the past few
months without this being worrisome. Releases occur often, the community is
growing, and most of the time users' questions do not remain unanswered.
The design discussions were fewer in the past quarter and people leading
these
efforts had quickly led them to consensus. As a result, we didn't have
lengthy
debates thus it's normal to see the activity of the dev@ and issues@ lists
slightly decreased (5% and 9% accordingly).
The number of closed issues and pull requests decreased by 19% which can be
explained by the low number of active committers (~12 during this period)
out
of which the majority pushed mostly individual contributions. A small
decrease
in closed issues can be attributed to those opened after applying static
code
analysis frameworks on the project that remain as tasks for the next
versions.
Re: Draft board report for October 2020
Posted by Stamatis Zampetakis <za...@gmail.com>.
That was a nice one Vladimir :)
I believe that personal contributions are valuable for the
project and we should definitely keep those coming.
At the same, we should try to improve our review capacity.
I think it is a good idea to call out reviewers by name, as
a small acknowledgement of their important work.
We can include the top-3 with each quarterly report;
let's start doing that!
On Sat, Oct 10, 2020 at 6:30 PM Vladimir Sitnikov <
sitnikov.vladimir@gmail.com> wrote:
> Julian>You must be an old C programmer, using 1 and 0 for true
>
> I still support Oracle DB 10g/11g apps, so booleans and filter() do not
> even exist in my world :)
>
> It turns out ./sqlsh is something that can execute "select count(*) from
> git_commits" directly (no models required).
> It would be nice to unify sqlline and sqlsh into a single command.
>
> Vladimir
>
Re: Draft board report for October 2020
Posted by Vladimir Sitnikov <si...@gmail.com>.
Julian>You must be an old C programmer, using 1 and 0 for true
I still support Oracle DB 10g/11g apps, so booleans and filter() do not
even exist in my world :)
It turns out ./sqlsh is something that can execute "select count(*) from
git_commits" directly (no models required).
It would be nice to unify sqlline and sqlsh into a single command.
Vladimir
Re: Draft board report for October 2020
Posted by Julian Hyde <jh...@apache.org>.
Stamatis,
Your "commits by non-committers" metric is a good one.
I think it might also be nice to call out, by name, the committers who
are committing non-committers' PRs. (Much more constructive than
shaming committers who are committing their own changes but no one
else's.)
Vladimir,
Very nice! You must be an old C programmer, using 1 and 0 for true and
false. May I suggest
select quarter_date
, count(*) filter (where is_committer) committers
, count(*) filter(where not is_commiter) non_committers
, count(*) total
from (
select cast(floor(commit_timestamp to quarter) as date) quarter_date
, c.author_timestamp > phonebook.first_commit as is_committer
from git_commits c
left join (
select committer
, min(commit_timestamp) first_commit
from git_commits
group by committer
) phonebook
on (c.author = phonebook.committer)
)
group by quarter_date
order by quarter_date;
Julian
On Fri, Oct 9, 2020 at 4:10 PM Vladimir Sitnikov
<si...@gmail.com> wrote:
>
> You are doing it all wrong! :)
>
> model.json:
>
> {
> "version": "1.0",
> "defaultSchema": "os",
> "schemas": [
> {
> "name": "os",
> "tables": [
> {
> "name": "git_commits",
> "type": "view",
> "sql": "select * from table(\"git_commits\"(true))"
> }
> ],
> "functions": [
> {
> "name": "git_commits",
> "className": "org.apache.calcite.adapter.os.GitCommitsTableFunction"
> }
> ]
> }
> ]
> }
>
>
> $ ./sqlline
>
> sqlline> !connect jdbc:calcite:model=model.json;lex=java admin admin
>
> select quarter_date
> , sum(is_committer) committers
> , sum(1 - is_committer) non_committers
> , count(*) total
> from (
> select cast(floor(commit_timestamp to quarter) as date) quarter_date
> , case when c.author_timestamp > phonebook.first_commit then
> 1 else 0 end is_committer
> from git_commits c
> left join (
> select committer
> , min(commit_timestamp) first_commit
> from git_commits
> group by committer
> ) phonebook
> on (c.author = phonebook.committer)
> )
> group by quarter_date
> order by quarter_date;
>
>
> +--------------+------------+----------------+-----------------+
> | quarter_date | committers | non_committers | total |
> +--------------+------------+----------------+-----------------+
> | 2012-04-01 | 60 | 5 | 65 |
> | 2012-07-01 | 64 | 0 | 64 |
> | 2012-10-01 | 50 | 1 | 51 |
> | 2013-01-01 | 100 | 1 | 101 |
> | 2013-04-01 | 136 | 0 | 136 |
> | 2013-07-01 | 129 | 3 | 132 |
> | 2013-10-01 | 127 | 6 | 133 |
> | 2014-01-01 | 219 | 26 | 245 |
> | 2014-04-01 | 167 | 16 | 183 |
> | 2014-07-01 | 124 | 18 | 142 |
> | 2014-10-01 | 86 | 23 | 109 |
> | 2015-01-01 | 89 | 25 | 114 |
> | 2015-04-01 | 92 | 30 | 122 |
> | 2015-07-01 | 78 | 34 | 112 |
> | 2015-10-01 | 80 | 42 | 122 |
> | 2016-01-01 | 133 | 23 | 156 |
> | 2016-04-01 | 98 | 27 | 125 |
> | 2016-07-01 | 51 | 27 | 78 |
> | 2016-10-01 | 71 | 35 | 106 |
> | 2017-01-01 | 90 | 48 | 138 |
> | 2017-04-01 | 65 | 52 | 117 |
> | 2017-07-01 | 39 | 36 | 75 |
> | 2017-10-01 | 44 | 46 | 90 |
> | 2018-01-01 | 43 | 43 | 86 |
> | 2018-04-01 | 33 | 67 | 100 |
> | 2018-07-01 | 115 | 49 | 164 |
> | 2018-10-01 | 47 | 44 | 91 |
> | 2019-01-01 | 80 | 68 | 148 |
> | 2019-04-01 | 69 | 80 | 149 |
> | 2019-07-01 | 70 | 93 | 163 |
> | 2019-10-01 | 122 | 101 | 223 |
> | 2020-01-01 | 129 | 51 | 180 |
> | 2020-04-01 | 106 | 69 | 175 |
> | 2020-07-01 | 126 | 42 | 168 |
> | 2020-10-01 | 75 | 2 | 77 |
> +--------------+------------+----------------+-----------------+
> 35 rows selected (0.265 seconds)
>
>
> Vladimir
Re: Draft board report for October 2020
Posted by Vladimir Sitnikov <si...@gmail.com>.
You are doing it all wrong! :)
model.json:
{
"version": "1.0",
"defaultSchema": "os",
"schemas": [
{
"name": "os",
"tables": [
{
"name": "git_commits",
"type": "view",
"sql": "select * from table(\"git_commits\"(true))"
}
],
"functions": [
{
"name": "git_commits",
"className": "org.apache.calcite.adapter.os.GitCommitsTableFunction"
}
]
}
]
}
$ ./sqlline
sqlline> !connect jdbc:calcite:model=model.json;lex=java admin admin
select quarter_date
, sum(is_committer) committers
, sum(1 - is_committer) non_committers
, count(*) total
from (
select cast(floor(commit_timestamp to quarter) as date) quarter_date
, case when c.author_timestamp > phonebook.first_commit then
1 else 0 end is_committer
from git_commits c
left join (
select committer
, min(commit_timestamp) first_commit
from git_commits
group by committer
) phonebook
on (c.author = phonebook.committer)
)
group by quarter_date
order by quarter_date;
+--------------+------------+----------------+-----------------+
| quarter_date | committers | non_committers | total |
+--------------+------------+----------------+-----------------+
| 2012-04-01 | 60 | 5 | 65 |
| 2012-07-01 | 64 | 0 | 64 |
| 2012-10-01 | 50 | 1 | 51 |
| 2013-01-01 | 100 | 1 | 101 |
| 2013-04-01 | 136 | 0 | 136 |
| 2013-07-01 | 129 | 3 | 132 |
| 2013-10-01 | 127 | 6 | 133 |
| 2014-01-01 | 219 | 26 | 245 |
| 2014-04-01 | 167 | 16 | 183 |
| 2014-07-01 | 124 | 18 | 142 |
| 2014-10-01 | 86 | 23 | 109 |
| 2015-01-01 | 89 | 25 | 114 |
| 2015-04-01 | 92 | 30 | 122 |
| 2015-07-01 | 78 | 34 | 112 |
| 2015-10-01 | 80 | 42 | 122 |
| 2016-01-01 | 133 | 23 | 156 |
| 2016-04-01 | 98 | 27 | 125 |
| 2016-07-01 | 51 | 27 | 78 |
| 2016-10-01 | 71 | 35 | 106 |
| 2017-01-01 | 90 | 48 | 138 |
| 2017-04-01 | 65 | 52 | 117 |
| 2017-07-01 | 39 | 36 | 75 |
| 2017-10-01 | 44 | 46 | 90 |
| 2018-01-01 | 43 | 43 | 86 |
| 2018-04-01 | 33 | 67 | 100 |
| 2018-07-01 | 115 | 49 | 164 |
| 2018-10-01 | 47 | 44 | 91 |
| 2019-01-01 | 80 | 68 | 148 |
| 2019-04-01 | 69 | 80 | 149 |
| 2019-07-01 | 70 | 93 | 163 |
| 2019-10-01 | 122 | 101 | 223 |
| 2020-01-01 | 129 | 51 | 180 |
| 2020-04-01 | 106 | 69 | 175 |
| 2020-07-01 | 126 | 42 | 168 |
| 2020-10-01 | 75 | 2 | 77 |
+--------------+------------+----------------+-----------------+
35 rows selected (0.265 seconds)
Vladimir
Re: Draft board report for October 2020
Posted by Stamatis Zampetakis <za...@gmail.com>.
The backlog is our usual problem; the number keeps increasing but it is
true that we don't have a better idea of how well/bad we are doing.
A metric sounds like a good idea and putting in the report every quarter
will help us have a permanent trace.
Percentage of open pull requests after three months is a good one.
Another could be the number commits from non-committers per quarter [1]
which would give something like the following:
Q1 2017:44
Q2 2017:43
Q3 2017:27
Q4 2017:36
Q1 2018:39
Q2 2018:49
Q3 2018:46
Q4 2018:45
Q1 2019:43
Q2 2019:53
Q3 2019:77
Q4 2019:87
Q1 2020:36
Q2 2020:52
Q3 2020:37
Q4 2020:1
[1] https://gist.github.com/zabetak/413cf1538ca9b026622e62596e094f6e
On Tue, Oct 6, 2020 at 8:37 PM Julian Hyde <jh...@apache.org> wrote:
> The report looks good.
>
> The backlog of pull requests continues to be a concern. I think we
> should track a metric so we know how we are doing, and strive to
> improve it. How about "percentage of pull requests that are open after
> three months"?
>
> Julian
>
> On Tue, Oct 6, 2020 at 7:37 AM Stamatis Zampetakis <za...@gmail.com>
> wrote:
> >
> > Thanks for the feedback guys!
> >
> > @Vladimir: Indeed the sentence does not make sense :)
> > It is a residual from another paragraph that I already removed.
> > Thanks for catching that.
> >
> > On Tue, Oct 6, 2020 at 10:54 AM Vladimir Sitnikov <
> > sitnikov.vladimir@gmail.com> wrote:
> >
> > > Stamatis> A small decrease
> > > Stamatis> in closed issues can be attributed to those opened after
> applying
> > > static
> > > Stamatis> code analysis frameworks
> > >
> > > Frankly speaking, it sounds puzzling.
> > > It is not clear how "opening new issues" might result in "decrease in
> > > closed issues".
> > >
> > > Vladimir
> > >
>
Re: Draft board report for October 2020
Posted by Julian Hyde <jh...@apache.org>.
The report looks good.
The backlog of pull requests continues to be a concern. I think we
should track a metric so we know how we are doing, and strive to
improve it. How about "percentage of pull requests that are open after
three months"?
Julian
On Tue, Oct 6, 2020 at 7:37 AM Stamatis Zampetakis <za...@gmail.com> wrote:
>
> Thanks for the feedback guys!
>
> @Vladimir: Indeed the sentence does not make sense :)
> It is a residual from another paragraph that I already removed.
> Thanks for catching that.
>
> On Tue, Oct 6, 2020 at 10:54 AM Vladimir Sitnikov <
> sitnikov.vladimir@gmail.com> wrote:
>
> > Stamatis> A small decrease
> > Stamatis> in closed issues can be attributed to those opened after applying
> > static
> > Stamatis> code analysis frameworks
> >
> > Frankly speaking, it sounds puzzling.
> > It is not clear how "opening new issues" might result in "decrease in
> > closed issues".
> >
> > Vladimir
> >
Re: Draft board report for October 2020
Posted by Stamatis Zampetakis <za...@gmail.com>.
Thanks for the feedback guys!
@Vladimir: Indeed the sentence does not make sense :)
It is a residual from another paragraph that I already removed.
Thanks for catching that.
On Tue, Oct 6, 2020 at 10:54 AM Vladimir Sitnikov <
sitnikov.vladimir@gmail.com> wrote:
> Stamatis> A small decrease
> Stamatis> in closed issues can be attributed to those opened after applying
> static
> Stamatis> code analysis frameworks
>
> Frankly speaking, it sounds puzzling.
> It is not clear how "opening new issues" might result in "decrease in
> closed issues".
>
> Vladimir
>
Re: Draft board report for October 2020
Posted by Vladimir Sitnikov <si...@gmail.com>.
Stamatis> A small decrease
Stamatis> in closed issues can be attributed to those opened after applying
static
Stamatis> code analysis frameworks
Frankly speaking, it sounds puzzling.
It is not clear how "opening new issues" might result in "decrease in
closed issues".
Vladimir
Re: Draft board report for October 2020
Posted by Ruben Q L <ru...@gmail.com>.
LGTM, thanks Stamatis!
On Tue, Oct 6, 2020 at 2:23 AM Michael Mior <mm...@apache.org> wrote:
> +1 LGTM Thanks!
> --
> Michael Mior
> mmior@apache.org
>
> Le lun. 5 oct. 2020 à 18:34, Francis Chuang <fr...@apache.org> a
> écrit :
> >
> > +1 Thanks, Stamatis!
> >
> > Francis
> >
> > On 6/10/2020 9:15 am, Haisheng Yuan wrote:
> > > Looks good to me, thanks!
> > >
> > > - Haisheng
> > >
> > > ------------------------------------------------------------------
> > > 发件人：Stamatis Zampetakis<za...@gmail.com>
> > > 日 期：2020年10月06日 06:04:06
> > > 收件人：<de...@calcite.apache.org>
> > > 主 题：Draft board report for October 2020
> > >
> > > Attached below is a draft of this month's board report. I plan to
> submit it
> > > on October 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:
> > > There are currently 51 committers and 23 PMC members in this project.
> > > The Committer-to-PMC ratio is roughly 7:3.
> > >
> > > Community changes, past quarter:
> > > - Ruben Quesada Lopez was added to the PMC on 2020-08-10
> > > - Rui Wang was added as committer on 2020-09-07
> > >
> > > ## Project Activity:
> > > Avatica Go 5.0.0 was released on 2020-07-16. It is a major release of
> > > Avatica
> > > Go with a number of improvements and a breaking change affecting
> connection
> > > metadata. Worth mentioning the support for batching query string
> parameters
> > > in
> > > the DSN, allowing updates to the server to be executed once Close() is
> > > called
> > > on the prepared statement.
> > >
> > > Calcite 1.24.0 was released on 2020-07-24, including more than 80
> resolved
> > > issues. Among those it’s worth highlighting some new features of the
> > > optimizer
> > > for more efficient search space pruning as well as the support of a
> new SQL
> > > dialect for Presto.
> > >
> > > Calcite 1.25.0 was released on 2020-08-22, with fewer but important
> features
> > > improving the parameterization of optimizer rules, adding support for
> new
> > > spatial functions, and interval expressions. The release also
> introduced a
> > > few
> > > breaking changes but so far the users seem to have embraced the
> changes.
> > >
> > > Members of the community gave talks at ApacheCon 2020, bringing to the
> > > surface
> > > Calcite through discussions about other projects. Although we didn’t
> have
> > > talks dedicated to Calcite, it is nice to receive mentions and witness
> the
> > > adoption of Calcite by other open source projects and people in
> Academia.
> > >
> > > ## Community Health:
> > > The overall activity in the community has slightly decreased in the
> past few
> > > months without this being worrisome. Releases occur often, the
> community is
> > > growing, and most of the time users' questions do not remain
> unanswered.
> > >
> > > The design discussions were fewer in the past quarter and people
> leading
> > > these
> > > efforts had quickly led them to consensus. As a result, we didn't have
> > > lengthy
> > > debates thus it's normal to see the activity of the dev@ and issues@
> lists
> > > slightly decreased (5% and 9% accordingly).
> > >
> > > The number of closed issues and pull requests decreased by 19% which
> can be
> > > explained by the low number of active committers (~12 during this
> period)
> > > out
> > > of which the majority pushed mostly individual contributions. A small
> > > decrease
> > > in closed issues can be attributed to those opened after applying
> static
> > > code
> > > analysis frameworks on the project that remain as tasks for the next
> > > versions.
> > >
>
Re: Draft board report for October 2020
Posted by Michael Mior <mm...@apache.org>.
+1 LGTM Thanks!
--
Michael Mior
mmior@apache.org
Le lun. 5 oct. 2020 à 18:34, Francis Chuang <fr...@apache.org> a écrit :
>
> +1 Thanks, Stamatis!
>
> Francis
>
> On 6/10/2020 9:15 am, Haisheng Yuan wrote:
> > Looks good to me, thanks!
> >
> > - Haisheng
> >
> > ------------------------------------------------------------------
> > 发件人：Stamatis Zampetakis<za...@gmail.com>
> > 日 期：2020年10月06日 06:04:06
> > 收件人：<de...@calcite.apache.org>
> > 主 题：Draft board report for October 2020
> >
> > Attached below is a draft of this month's board report. I plan to submit it
> > on October 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:
> > There are currently 51 committers and 23 PMC members in this project.
> > The Committer-to-PMC ratio is roughly 7:3.
> >
> > Community changes, past quarter:
> > - Ruben Quesada Lopez was added to the PMC on 2020-08-10
> > - Rui Wang was added as committer on 2020-09-07
> >
> > ## Project Activity:
> > Avatica Go 5.0.0 was released on 2020-07-16. It is a major release of
> > Avatica
> > Go with a number of improvements and a breaking change affecting connection
> > metadata. Worth mentioning the support for batching query string parameters
> > in
> > the DSN, allowing updates to the server to be executed once Close() is
> > called
> > on the prepared statement.
> >
> > Calcite 1.24.0 was released on 2020-07-24, including more than 80 resolved
> > issues. Among those it’s worth highlighting some new features of the
> > optimizer
> > for more efficient search space pruning as well as the support of a new SQL
> > dialect for Presto.
> >
> > Calcite 1.25.0 was released on 2020-08-22, with fewer but important features
> > improving the parameterization of optimizer rules, adding support for new
> > spatial functions, and interval expressions. The release also introduced a
> > few
> > breaking changes but so far the users seem to have embraced the changes.
> >
> > Members of the community gave talks at ApacheCon 2020, bringing to the
> > surface
> > Calcite through discussions about other projects. Although we didn’t have
> > talks dedicated to Calcite, it is nice to receive mentions and witness the
> > adoption of Calcite by other open source projects and people in Academia.
> >
> > ## Community Health:
> > The overall activity in the community has slightly decreased in the past few
> > months without this being worrisome. Releases occur often, the community is
> > growing, and most of the time users' questions do not remain unanswered.
> >
> > The design discussions were fewer in the past quarter and people leading
> > these
> > efforts had quickly led them to consensus. As a result, we didn't have
> > lengthy
> > debates thus it's normal to see the activity of the dev@ and issues@ lists
> > slightly decreased (5% and 9% accordingly).
> >
> > The number of closed issues and pull requests decreased by 19% which can be
> > explained by the low number of active committers (~12 during this period)
> > out
> > of which the majority pushed mostly individual contributions. A small
> > decrease
> > in closed issues can be attributed to those opened after applying static
> > code
> > analysis frameworks on the project that remain as tasks for the next
> > versions.
> >
Re: Draft board report for October 2020
Posted by Francis Chuang <fr...@apache.org>.
+1 Thanks, Stamatis!
Francis
On 6/10/2020 9:15 am, Haisheng Yuan wrote:
> Looks good to me, thanks!
>
> - Haisheng
>
> ------------------------------------------------------------------
> 发件人：Stamatis Zampetakis<za...@gmail.com>
> 日 期：2020年10月06日 06:04:06
> 收件人：<de...@calcite.apache.org>
> 主 题：Draft board report for October 2020
>
> Attached below is a draft of this month's board report. I plan to submit it
> on October 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:
> There are currently 51 committers and 23 PMC members in this project.
> The Committer-to-PMC ratio is roughly 7:3.
>
> Community changes, past quarter:
> - Ruben Quesada Lopez was added to the PMC on 2020-08-10
> - Rui Wang was added as committer on 2020-09-07
>
> ## Project Activity:
> Avatica Go 5.0.0 was released on 2020-07-16. It is a major release of
> Avatica
> Go with a number of improvements and a breaking change affecting connection
> metadata. Worth mentioning the support for batching query string parameters
> in
> the DSN, allowing updates to the server to be executed once Close() is
> called
> on the prepared statement.
>
> Calcite 1.24.0 was released on 2020-07-24, including more than 80 resolved
> issues. Among those it’s worth highlighting some new features of the
> optimizer
> for more efficient search space pruning as well as the support of a new SQL
> dialect for Presto.
>
> Calcite 1.25.0 was released on 2020-08-22, with fewer but important features
> improving the parameterization of optimizer rules, adding support for new
> spatial functions, and interval expressions. The release also introduced a
> few
> breaking changes but so far the users seem to have embraced the changes.
>
> Members of the community gave talks at ApacheCon 2020, bringing to the
> surface
> Calcite through discussions about other projects. Although we didn’t have
> talks dedicated to Calcite, it is nice to receive mentions and witness the
> adoption of Calcite by other open source projects and people in Academia.
>
> ## Community Health:
> The overall activity in the community has slightly decreased in the past few
> months without this being worrisome. Releases occur often, the community is
> growing, and most of the time users' questions do not remain unanswered.
>
> The design discussions were fewer in the past quarter and people leading
> these
> efforts had quickly led them to consensus. As a result, we didn't have
> lengthy
> debates thus it's normal to see the activity of the dev@ and issues@ lists
> slightly decreased (5% and 9% accordingly).
>
> The number of closed issues and pull requests decreased by 19% which can be
> explained by the low number of active committers (~12 during this period)
> out
> of which the majority pushed mostly individual contributions. A small
> decrease
> in closed issues can be attributed to those opened after applying static
> code
> analysis frameworks on the project that remain as tasks for the next
> versions.
>
Re: Draft board report for October 2020
Posted by Haisheng Yuan <h....@alibaba-inc.com>.
Looks good to me, thanks!
- Haisheng
------------------------------------------------------------------
发件人：Stamatis Zampetakis<za...@gmail.com>
日 期：2020年10月06日 06:04:06
收件人：<de...@calcite.apache.org>
主 题：Draft board report for October 2020
Attached below is a draft of this month's board report. I plan to submit it
on October 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:
There are currently 51 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- Ruben Quesada Lopez was added to the PMC on 2020-08-10
- Rui Wang was added as committer on 2020-09-07
## Project Activity:
Avatica Go 5.0.0 was released on 2020-07-16. It is a major release of
Avatica
Go with a number of improvements and a breaking change affecting connection
metadata. Worth mentioning the support for batching query string parameters
in
the DSN, allowing updates to the server to be executed once Close() is
called
on the prepared statement.
Calcite 1.24.0 was released on 2020-07-24, including more than 80 resolved
issues. Among those it’s worth highlighting some new features of the
optimizer
for more efficient search space pruning as well as the support of a new SQL
dialect for Presto.
Calcite 1.25.0 was released on 2020-08-22, with fewer but important features
improving the parameterization of optimizer rules, adding support for new
spatial functions, and interval expressions. The release also introduced a
few
breaking changes but so far the users seem to have embraced the changes.
Members of the community gave talks at ApacheCon 2020, bringing to the
surface
Calcite through discussions about other projects. Although we didn’t have
talks dedicated to Calcite, it is nice to receive mentions and witness the
adoption of Calcite by other open source projects and people in Academia.
## Community Health:
The overall activity in the community has slightly decreased in the past few
months without this being worrisome. Releases occur often, the community is
growing, and most of the time users' questions do not remain unanswered.
The design discussions were fewer in the past quarter and people leading
these
efforts had quickly led them to consensus. As a result, we didn't have
lengthy
debates thus it's normal to see the activity of the dev@ and issues@ lists
slightly decreased (5% and 9% accordingly).
The number of closed issues and pull requests decreased by 19% which can be
explained by the low number of active committers (~12 during this period)
out
of which the majority pushed mostly individual contributions. A small
decrease
in closed issues can be attributed to those opened after applying static
code
analysis frameworks on the project that remain as tasks for the next
versions.