Re: [DISCUSS] Towards Calcite 1.37.0

[Francis Chuang]

t;

This PR solves two problems at once. I initially started by

solving 3522,

but then I realized that the solution uncovers many bugs in 6169,

so I

solved that one as well. Just days ago someone filed
https://issues.apache.org/jira/browse/CALCITE-6366 for this very

issue.



   *
3522 solves the problem where Calcite limits DECIMAL literals to

64 bits.

However, even the default DECIMAL implementation in Calcite

supports 128

bits, and some SQL dialects go even further (Postgres has billions

of

digits of precision). With this change there are no limits to the

precision

of a DECIMAL literal, and the limits come from the Calcite

typeSystem in

use.
   *
6366 solves another problem related to the first issue described

above,

6322, where narrowing casts (that convert a numeric value to a

numeric

value with fewer bits) do not report errors on overflow. This is

another

long-standing bug in Calcite.

I will try to break this into two separate PRs that have to be

merged in

order; I will start with 6169. Maybe this will make it more

palatable for

the reviewers.

Besides these 3 PRs, I have one more PR that I would like to land

in 1.37,

which is not a bugfix, but a new feature, so perhaps it's less

urgent.

[CALCITE-6071] RexCall should carry source position information

for runtime

error reporting<https://github.com/apache/calcite/pull/3506> is a
relatively large PR, which adds source position information to

RexCall and

AggregateCall nodes. This is useful when a runtime error happens,

like a

division by 0. Using this information the runtime can report which
division in the program failed. Without this, debugging may be very
difficult, especially when the program is large and can have many

division

operations, some hidden in operations like STDDEV_SAMP. This PR

does not

affect in any way the semantics of Calcite programs, it's a no-op

for

almost everyone. But it does touch many files, because it has to

add new

constructors for these classes and make sure that the information

is

available when the constructors are being invoked. At this point

there are

no users of this information in the Calcite codebase, but once the

PR is

merged we can use it even in the existing evaluator (that will

also require

significant work, since the evaluator itself does not expect source
position information).

Thank you,
Mihai

____________
From: Francis Chuang 
Sent: Wednesday, April 17, 2024 9:05 PM
To: dev@calcite.apache.org 
Subject: Re: [DISCUSS] Towards Calcite 1.37.0

I agree that it would be good to cut a release soon, as there

haven't

been too many commits in the last couple of days.

I think it would be great for Sergey to set a deadline for the last
commits to be accepted, close the main branch and start the release
process. As Sergey is RM for the release, it would be best for him

to

set the date as to when the main branch should be closed.

On 18/04/2024 12:55 pm, Benchao Li wrote:

May I ask what's the status of releasing 1.37.0, since upgrading

to

Avatica 1.25 has been done 9 days ago, I would assume that there

are

no blockers now?

I know many of us would like to clear some of the PR backlog

before a

release, however it would be better to have some balance between
clearing PR backlog and rolling out releases regularly. It's

been a

bit more than 5 months since our last Calcite release (1.36.0 on
2023-11-10), and 2 months after I kicked off this thread.

What do you think?

Francis Chuang  于2024年4月9日周二 05:49写道：


+1 I think that's a good idea and will help clear some of the PR

backlog.


On 9/04/2024 7:47 am, Sergey Nuyanzin wrote:

I think it would would make sense if they are already ready to

be

merged

Thanks for the suggestion

what do you think if we reserve about 2-3 days for this

activity?

I would also encourage committers to merge such bug fixes if

any




On Mon, Apr 8, 2024 at 11:36 PM Mihai Budiu 

wrote:



Can we do another quick pass over the open PRs, or is it too

late?

Since we started the process a bunch of bug fixes were

submitted, and

some

of them may be easy to merge.

Mihai

From: Sergey Nuyanzin 
Sent: Monday, April 8, 2024 2:32 PM
To: dev@calcite.apache.org 
Subject: Re: [DISCUSS] Towards Calcite 1.37.0

Upgrade of Avatica is done at CALCITE-6356 [1], thanks a lot

for

review

You can go forward with PRs if there still any

If there is no objections  I'm going to start steps to

prepare and

create

an RC tomorrow

[1] https://issues.apache.org/jira/browse/CALCITE-6356

On Mon, Apr 8, 2024 at 8:14 PM Mihai Budiu 

wrote:



Hello,

I am assuming that (one of) the next steps towards 1.37 will

be a PR

which

upgrades Avatica to 1.25.
Is anyone working on that?
After that is merged I plan to merge two PRs which re-enable

the

tests

that

were disabled temporarily.

Thank you,
Mihai


On Mon, Mar 18, 2024 at 9:48 AM Mihai Budiu <

mbu...@gmail.com>

wrote:



This would 

Re: [VOTE] Release Apache Calcite 1.37.0 (release candidate 4)

[Francis Chuang]

My vote is: +1 (binding)

- Verified GPG signature - OK
- Verified SHA512 - OK
- Diffed source release and git repository - OK
- Checked release notes on tag 
(https://github.com/apache/calcite/blob/calcite-1.37.0-rc4/site/_docs/history.md) 
- OK

- Checked year and versions in NOTICE, README and HOWTO - OK
- Ran tests (gradle check) - OK
- Spot checked Nexus artifacts - OK

Environments:
Eclipse-temurin:8 docker container in WSL2 (Ubuntu 22.04.4) on Windows 
11 23h2


Eclipse-temurin:19 docker container in WSL2 (Ubuntu 22.04.4) on Windows 
11 23h2


$ docker version
Client:
 Cloud integration: v1.0.35+desktop.13
 Version:   26.0.0
 API version:   1.45
 Go version:go1.21.8
 Git commit:2ae903e
 Built: Wed Mar 20 15:16:45 2024
 OS/Arch:   linux/amd64
 Context:   default

Server: Docker Desktop
 Engine:
  Version:  26.0.0
  API version:  1.45 (minimum version 1.24)
  Go version:   go1.21.8
  Git commit:   8b79278
  Built:Wed Mar 20 15:18:01 2024
  OS/Arch:  linux/amd64
  Experimental: false
 containerd:
  Version:  1.6.28
  GitCommit:ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:  1.1.12
  GitCommit:v1.1.12-0-g51d5e94
 docker-init:
  Version:  0.19.0
  GitCommit:de40ad0

$ gradle -v


Gradle 7.6.1


Build time:   2023-02-24 13:54:42 UTC
Revision: 3905fe8ac072bbd925c70ddbf4463341f4b4

Kotlin:   1.7.10
Groovy:   3.0.13
Ant:  Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM:  19.0.2 (Eclipse Adoptium 19.0.2+7)
OS:   Linux 5.15.146.1-microsoft-standard-WSL2 amd64

$ java -version
openjdk version "1.8.0_402"
OpenJDK Runtime Environment (Temurin)(build 1.8.0_402-b06)
OpenJDK 64-Bit Server VM (Temurin)(build 25.402-b06, mixed mode)

$ java -version
openjdk version "19.0.2" 2023-01-17
OpenJDK Runtime Environment Temurin-19.0.2+7 (build 19.0.2+7)
OpenJDK 64-Bit Server VM Temurin-19.0.2+7 (build 19.0.2+7, mixed mode, 
sharing)


Francis

On 30/04/2024 6:35 pm, Stamatis Zampetakis wrote:

Ubuntu 20.04.6 LTS, jdk1.8.0_261, Gradle wrapper, Gradle 7.6.1

  * Checked signatures and checksums OK
  * Checked diff between repo and artifacts OK
  * Checked README, NOTICE, LICENSE OK
  * All source files have ASF headers OK ( grep -RiL "Licensed to the
Apache Software Foundation")
  * No unexpected binary files OK (find . -type f -exec file {} \; |
grep -v text)
  * Checked structure of staged maven repo for calcite-core [1] OK
  * Checked LICENSE, NOTICE, signature, and checksum for
calcite-core-1.37.0.jar from staged maven repo [1] OK
  * Built from git tag and run tests (./gradlew build) OK
  * Built from source artifacts and run tests (gradle build) OK

+1 (binding)

For the ASM problem, I would suggest opening a JIRA ticket and
continuing the discussion there. I found the previous discussion [2]
but not a ticket for this. We should try to keep vote threads as clean
as possible and keep technical exchanges on separate threads/tickets.
The main deliverable of this vote is the source package distribution
so I don't consider this a blocker for the release especially since
this has popped up before and was left untreated.

Best,
Stamatis

[1] 
https://repository.apache.org/content/repositories/orgapachecalcite-1230/org/apache/calcite/calcite-core/1.37.0/
[2] https://lists.apache.org/thread/o736wz4qnr4l285bj5gv073cy0qll9t0

On Tue, Apr 30, 2024 at 9:50 AM Ruben Q L  wrote:


Thanks Guillaume for checking this!
When I looked at this issue on 1.36, I had the impression that assertions
might have a role to play in the error, but I could not confirm this
hypothesis.
IMO this smells like a JDK bug (or at least it looks like other resolved
issues); note that it seems we had some similar problems in the past with
older Java8 versions [1].

Independently of the root cause, would it unblock the release process if we
just remove the problematic asserts, or if we substitute them with an
equivalent `if (...) throw new IllegalStateException("...");` ?

Best,
Ruben

[1]
https://github.com/apache/calcite/blob/1506857f404037b63dfd8a11880393b767bd1544/build.gradle.kts#L98



On Mon, Apr 29, 2024 at 11:26 PM Sergey Nuyanzin 
wrote:


Hi Guilluame,

I played a bit more and I realised that if from commit above I just remove
one line with assert (assert map != null)
then ArrayIndexOutOfBoundsException disappears

same for current main branch, if I remove all lines from SqlFunctions with
assert (now there are 3 such lines) then
ArrayIndexOutOfBoundsException disappears

Thus,  it does not look like a Calcite issue, more like a problem on ASM
side
please correct me if I'm wrong

On Mon, Apr 29, 2024 at 10:33 PM Sergey Nuyanzin 
wrote:


i follow the procedure described here

Re: [VOTE] Release Apache Calcite 1.37.0 (release candidate 2)

[Francis Chuang]

Thanks for making rc2 available for voting, Sergey and thanks to 
Stamatis for fixing the bug causing tests to fail when run from the 
source distribution.


My vote is: +1 (binding)

- Verified GPG signature - OK
- Verified SHA512 - OK
- Diffed source release and git repository - OK
- Checked release notes on tag 
(https://github.com/apache/calcite/blob/calcite-1.37.0-rc2/site/_docs/history.md) 
- OK

- Checked year and versions in NOTICE, README and HOWTO - OK
- Ran tests (gradle check) - OK
- Spot checked Nexus artifacts - OK

Repeating my comment from the previous vote regarding some contributors 
being listed by their username rather than their full name: I think it 
would be better to put in their real names if they are known. These can 
usually be retrieved from their GitHub profiles. This is a minor issue 
that can be dealt with after the release.


Environment:
Eclipse-temurin:8 docker container in WSL2 (Ubuntu 22.04.4) on Windows 
11 23h2


$ docker version
Client:
 Cloud integration: v1.0.35+desktop.13
 Version:   26.0.0
 API version:   1.45
 Go version:go1.21.8
 Git commit:2ae903e
 Built: Wed Mar 20 15:16:45 2024
 OS/Arch:   linux/amd64
 Context:   default

Server: Docker Desktop
 Engine:
  Version:  26.0.0
  API version:  1.45 (minimum version 1.24)
  Go version:   go1.21.8
  Git commit:   8b79278
  Built:Wed Mar 20 15:18:01 2024
  OS/Arch:  linux/amd64
  Experimental: false
 containerd:
  Version:  1.6.28
  GitCommit:ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:  1.1.12
  GitCommit:v1.1.12-0-g51d5e94
 docker-init:
  Version:  0.19.0
  GitCommit:de40ad0

$ gradle -v


Gradle 7.6.1


Build time:   2023-02-24 13:54:42 UTC
Revision: 3905fe8ac072bbd925c70ddbf4463341f4b4

Kotlin:   1.7.10
Groovy:   3.0.13
Ant:  Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM:  1.8.0_402 (Temurin 25.402-b06)
OS:   Linux 5.15.146.1-microsoft-standard-WSL2 amd64

$ java -version
openjdk version "1.8.0_402"
OpenJDK Runtime Environment (Temurin)(build 1.8.0_402-b06)
OpenJDK 64-Bit Server VM (Temurin)(build 25.402-b06, mixed mode)

Francis
On 26/04/2024 6:28 am, Sergey Nuyanzin wrote:

Hi all,

I have created a build for Apache Calcite 1.37.0, release
candidate 2 (there was an issue in subject name and actual rc number, so
for safety it is 2).

Thanks to everyone who has contributed to this release.

You can read the release notes here:
https://github.com/apache/calcite/blob/calcite-1.37.0-rc2/site/_docs/history.md

The commit to be voted upon:
https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=6d8175111ec72f65cb12815d5d519680f62dfd08

Its hash is 6d8175111ec72f65cb12815d5d519680f62dfd08

Tag:
https://github.com/apache/calcite/tree/calcite-1.37.0-rc2

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.37.0-rc2
(revision 68794)

The hashes of the artifacts are as follows:
373665630145ac52221eeec8456c295c868dfe6a15ded4b7d92e929db769d3c13d21409478c57b93671bca703bf183a24069def42d33d078a5cdec6a2ec69368
*apache-calcite-1.37.0-src.tar.gz

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1228/org/apache/calcite/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/snuyanzin.asc
https://www.apache.org/dist/calcite/KEYS

To create the jars and test Apache Calcite: "gradle build"
(requires an appropriate Gradle/JDK installation)

Please vote on releasing this package as Apache Calcite 1.37.0.

The vote is open for the next 72 hours(I think we can extend it a bit
given the fact that there is a weekend soon) and passes if a majority of at
least three +1 PMC votes are cast.

[ ] +1 Release this package as Apache Calcite 1.37.0
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...

Here is my vote:

+1 (binding)

Re: [VOTE] Release Apache Calcite 1.37.0 (release candidate 1)

[Francis Chuang]

Thanks for being RM for this release, Sergey!

My vote is: +1 (binding)

- Verified GPG signature - OK
- Verified SHA512 - OK
- Diffed source release and git repository - OK
- Checked release notes on tag 
(https://github.com/apache/calcite/blob/calcite-1.37.0-rc0/site/_docs/history.md) 
- OK

- Checked year and versions in NOTICE, README and HOWTO - OK
- Ran tests (gradle check) - OK
- Spot checked Nexus artifacts - OK

Minor issue with the release notes that should be fixed after the 
release: Some of the contributors are listed as their GitHub usernames, 
I think it would be better to put in their real names if they are known. 
These can usually be retrieved from their GitHub profiles.


Environment:
Eclipse-temurin:8 docker container in WSL2 (Ubuntu 22.04.4) on Windows 
11 23h2


$ docker version
Client:
 Cloud integration: v1.0.35+desktop.13
 Version:   26.0.0
 API version:   1.45
 Go version:go1.21.8
 Git commit:2ae903e
 Built: Wed Mar 20 15:16:45 2024
 OS/Arch:   linux/amd64
 Context:   default

Server: Docker Desktop
 Engine:
  Version:  26.0.0
  API version:  1.45 (minimum version 1.24)
  Go version:   go1.21.8
  Git commit:   8b79278
  Built:Wed Mar 20 15:18:01 2024
  OS/Arch:  linux/amd64
  Experimental: false
 containerd:
  Version:  1.6.28
  GitCommit:ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:  1.1.12
  GitCommit:v1.1.12-0-g51d5e94
 docker-init:
  Version:  0.19.0
  GitCommit:de40ad0

$ gradle -v


Gradle 7.6.1


Build time:   2023-02-24 13:54:42 UTC
Revision: 3905fe8ac072bbd925c70ddbf4463341f4b4

Kotlin:   1.7.10
Groovy:   3.0.13
Ant:  Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM:  1.8.0_402 (Temurin 25.402-b06)
OS:   Linux 5.15.146.1-microsoft-standard-WSL2 amd64

$ java -version
openjdk version "1.8.0_402"
OpenJDK Runtime Environment (Temurin)(build 1.8.0_402-b06)
OpenJDK 64-Bit Server VM (Temurin)(build 25.402-b06, mixed mode)

Francis

On 23/04/2024 9:18 am, Sergey Nuyanzin wrote:

Hi all,

I have created a build for Apache Calcite 1.37.0, release
candidate 0.

Thanks to everyone who has contributed to this release.

You can read the release notes here:
https://github.com/apache/calcite/blob/calcite-1.37.0-rc0/site/_docs/history.md

The commit to be voted upon:
https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=53fd905eb4c730b4bedd49fa6569d5b0de47f021

Its hash is 53fd905eb4c730b4bedd49fa6569d5b0de47f021

Tag:
https://github.com/apache/calcite/tree/calcite-1.37.0-rc0

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.37.0-rc0
(revision 68720)

The hashes of the artifacts are as follows:
b044fb94fd60710142edfe348ff20bbdc7e43f3d70a68b6520b65dc8fb2fe53f0ecf6b5d03b199b3212e9064a7dd04fb3995a9cd09cb8864a7bfdb5617feefbb
*apache-calcite-1.37.0-src.tar.gz

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1225/org/apache/calcite/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/snuyanzin.asc
https://www.apache.org/dist/calcite/KEYS

To create the jars and test Apache Calcite: "gradle build"
(requires an appropriate Gradle/JDK installation)

Please vote on releasing this package as Apache Calcite 1.37.0.

The vote is open for the next 72 hours and passes if a majority of at
least three +1 PMC votes are cast.

[ ] +1 Release this package as Apache Calcite 1.37.0
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...

Here is my vote:

+1 (binding)

Re: [DISCUSS] Towards Calcite 1.37.0

[Francis Chuang]

I agree that it would be good to cut a release soon, as there haven't 
been too many commits in the last couple of days.


I think it would be great for Sergey to set a deadline for the last 
commits to be accepted, close the main branch and start the release 
process. As Sergey is RM for the release, it would be best for him to 
set the date as to when the main branch should be closed.


On 18/04/2024 12:55 pm, Benchao Li wrote:

May I ask what's the status of releasing 1.37.0, since upgrading to
Avatica 1.25 has been done 9 days ago, I would assume that there are
no blockers now?

I know many of us would like to clear some of the PR backlog before a
release, however it would be better to have some balance between
clearing PR backlog and rolling out releases regularly. It's been a
bit more than 5 months since our last Calcite release (1.36.0 on
2023-11-10), and 2 months after I kicked off this thread.

What do you think?

Francis Chuang  于2024年4月9日周二 05:49写道：


+1 I think that's a good idea and will help clear some of the PR backlog.

On 9/04/2024 7:47 am, Sergey Nuyanzin wrote:

I think it would would make sense if they are already ready to be merged
Thanks for the suggestion

what do you think if we reserve about 2-3 days for this activity?
I would also encourage committers to merge such bug fixes if any



On Mon, Apr 8, 2024 at 11:36 PM Mihai Budiu  wrote:


Can we do another quick pass over the open PRs, or is it too late?
Since we started the process a bunch of bug fixes were submitted, and some
of them may be easy to merge.

Mihai

From: Sergey Nuyanzin 
Sent: Monday, April 8, 2024 2:32 PM
To: dev@calcite.apache.org 
Subject: Re: [DISCUSS] Towards Calcite 1.37.0

Upgrade of Avatica is done at CALCITE-6356 [1], thanks a lot for review
You can go forward with PRs if there still any

If there is no objections  I'm going to start steps to prepare and create
an RC tomorrow

[1] https://issues.apache.org/jira/browse/CALCITE-6356

On Mon, Apr 8, 2024 at 8:14 PM Mihai Budiu  wrote:


Hello,

I am assuming that (one of) the next steps towards 1.37 will be a PR

which

upgrades Avatica to 1.25.
Is anyone working on that?
After that is merged I plan to merge two PRs which re-enable the tests

that

were disabled temporarily.

Thank you,
Mihai


On Mon, Mar 18, 2024 at 9:48 AM Mihai Budiu  wrote:


This would be great, I am fixing two very basic bugs.
Was busy with some other stuff, so I didn't have time to figure out how

to

submit the PRs so that they pass, if anyone has more detailed

instructions

I would be very happy. Otherwise I will dig into it.

Mihai
--
*From:* Francis Chuang 
*Sent:* Sunday, March 17, 2024 2:44 PM
*To:* dev@calcite.apache.org 
*Subject:* Re: [DISCUSS] Towards Calcite 1.37.0

Hey everyone,

I just wanted to jump in regarding CALCITE-6248 [1] and CALCITE-6282

(no

corresponding PRs in the Calcite repo yet).

The corresponding PRs in the Avatica repo are:
- https://github.com/apache/calcite-avatica/pull/238
- https://github.com/apache/calcite-avatica/pull/241

As the issue will require changes to both Calcite and Avatica in a
coordinated fashion, what do you guys think about releasing Avatica
1.25.0 first? I can be RM for the Avatica release.

Mihai, can you please confirm if this approach works for you?

Discussion for getting changes simultaneously into both Avatica and
Calcite is here [2].

Francis

[1] https://github.com/apache/calcite/pull/3708
[2] https://lists.apache.org/thread/5w3ry3zbm7671ffp4pxh7lx6cgc5r3tq

On 13/03/2024 10:07 pm, Benchao Li wrote:

Thank you, Hongyu, for volunteering to be a release manager.

What's worth to mention is that to be a release manager does not
require PMC membership nor being a committer, and it is a good chance
to be involved in community activities apart from code/discussion,
which would be a good additional credit for being considered as
committer or PMC member candidate.

Hongyu Guo  于2024年3月13日周三 11:29写道：


I would like to take on the role of RM for one release

On Thu, Mar 7, 2024 at 2:58 AM Alessandro Solimando <
alessandro.solima...@gmail.com> wrote:


Hey Sergey,
thanks for being the release manager for 1.37.0.

I have added fixVersion=1.37.0 to CALCITE-2040
<https://issues.apache.org/jira/browse/CALCITE-2040>, as its

associated PR

<https://github.com/apache/calcite/pull/3666> is in good shape

IMO,

and we

are trying to get it done shortly with Hongyu.

Best regards,
Alessandro

On Wed, 6 Mar 2024 at 16:49, Sergey Nuyanzin 

wrote:



Updates about 1.37.0 releasing

According to our Jira dashboard [1] and Github [2], there
are 17 pending issues that could / should be part of the release.
I'd propose to make a collective effort to try to clean up our

1.37.0

backlog and merge the PRs which are in a good state. I'd propose

to

aim for about 2 weeks to release 1.37.0, this will give us about
some time to clean up pending PRs for the next version. W

[jira] [Created] (CALCITE-6360) Add .asf.yaml to calcite-avatica-go repository

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6360:
---

 Summary: Add .asf.yaml to calcite-avatica-go repository
 Key: CALCITE-6360
 URL: https://issues.apache.org/jira/browse/CALCITE-6360
 Project: Calcite
  Issue Type: Task
  Components: avatica-go
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: avatica-go-5.4.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (CALCITE-6359) Update GitHub Actions workflows to use docker compose v2

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6359:
---

 Summary: Update GitHub Actions workflows to use docker compose v2
 Key: CALCITE-6359
 URL: https://issues.apache.org/jira/browse/CALCITE-6359
 Project: Calcite
  Issue Type: Task
  Components: avatica, avatica-go, core
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: 1.37.0, avatica-go-5.4.0, avatica-1.26.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Towards Calcite 1.37.0

[Francis Chuang]

+1 I think that's a good idea and will help clear some of the PR backlog.

On 9/04/2024 7:47 am, Sergey Nuyanzin wrote:

I think it would would make sense if they are already ready to be merged
Thanks for the suggestion

what do you think if we reserve about 2-3 days for this activity?
I would also encourage committers to merge such bug fixes if any



On Mon, Apr 8, 2024 at 11:36 PM Mihai Budiu  wrote:


Can we do another quick pass over the open PRs, or is it too late?
Since we started the process a bunch of bug fixes were submitted, and some
of them may be easy to merge.

Mihai

From: Sergey Nuyanzin 
Sent: Monday, April 8, 2024 2:32 PM
To: dev@calcite.apache.org 
Subject: Re: [DISCUSS] Towards Calcite 1.37.0

Upgrade of Avatica is done at CALCITE-6356 [1], thanks a lot for review
You can go forward with PRs if there still any

If there is no objections  I'm going to start steps to prepare and create
an RC tomorrow

[1] https://issues.apache.org/jira/browse/CALCITE-6356

On Mon, Apr 8, 2024 at 8:14 PM Mihai Budiu  wrote:


Hello,

I am assuming that (one of) the next steps towards 1.37 will be a PR

which

upgrades Avatica to 1.25.
Is anyone working on that?
After that is merged I plan to merge two PRs which re-enable the tests

that

were disabled temporarily.

Thank you,
Mihai


On Mon, Mar 18, 2024 at 9:48 AM Mihai Budiu  wrote:


This would be great, I am fixing two very basic bugs.
Was busy with some other stuff, so I didn't have time to figure out how

to

submit the PRs so that they pass, if anyone has more detailed

instructions

I would be very happy. Otherwise I will dig into it.

Mihai
--
*From:* Francis Chuang 
*Sent:* Sunday, March 17, 2024 2:44 PM
*To:* dev@calcite.apache.org 
*Subject:* Re: [DISCUSS] Towards Calcite 1.37.0

Hey everyone,

I just wanted to jump in regarding CALCITE-6248 [1] and CALCITE-6282

(no

corresponding PRs in the Calcite repo yet).

The corresponding PRs in the Avatica repo are:
- https://github.com/apache/calcite-avatica/pull/238
- https://github.com/apache/calcite-avatica/pull/241

As the issue will require changes to both Calcite and Avatica in a
coordinated fashion, what do you guys think about releasing Avatica
1.25.0 first? I can be RM for the Avatica release.

Mihai, can you please confirm if this approach works for you?

Discussion for getting changes simultaneously into both Avatica and
Calcite is here [2].

Francis

[1] https://github.com/apache/calcite/pull/3708
[2] https://lists.apache.org/thread/5w3ry3zbm7671ffp4pxh7lx6cgc5r3tq

On 13/03/2024 10:07 pm, Benchao Li wrote:

Thank you, Hongyu, for volunteering to be a release manager.

What's worth to mention is that to be a release manager does not
require PMC membership nor being a committer, and it is a good chance
to be involved in community activities apart from code/discussion,
which would be a good additional credit for being considered as
committer or PMC member candidate.

Hongyu Guo  于2024年3月13日周三 11:29写道：


I would like to take on the role of RM for one release

On Thu, Mar 7, 2024 at 2:58 AM Alessandro Solimando <
alessandro.solima...@gmail.com> wrote:


Hey Sergey,
thanks for being the release manager for 1.37.0.

I have added fixVersion=1.37.0 to CALCITE-2040
<https://issues.apache.org/jira/browse/CALCITE-2040>, as its

associated PR

<https://github.com/apache/calcite/pull/3666> is in good shape

IMO,

and we

are trying to get it done shortly with Hongyu.

Best regards,
Alessandro

On Wed, 6 Mar 2024 at 16:49, Sergey Nuyanzin 

wrote:



Updates about 1.37.0 releasing

According to our Jira dashboard [1] and Github [2], there
are 17 pending issues that could / should be part of the release.
I'd propose to make a collective effort to try to clean up our

1.37.0

backlog and merge the PRs which are in a good state. I'd propose

to

aim for about 2 weeks to release 1.37.0, this will give us about
some time to clean up pending PRs for the next version. What do

you

think?


And contributors, if you have any work that is in good shape and

want

to be included in 1.37.0, please mark the fixVersion to 1.37.0,

this

will inform the release manager, and we'll try our best to get it

in.


A quick update on the current status for issues targeted 1.37.0
We need more reviewers for #2

#1. Issues already have reviewers, and seems promising to be

merged

shortly

https://issues.apache.org/jira/browse/CALCITE-6138
https://issues.apache.org/jira/browse/CALCITE-6015
https://issues.apache.org/jira/browse/CALCITE-6283
https://issues.apache.org/jira/browse/CALCITE-5607

   #2. Issues has been reviewed, and needs another reviewer
https://issues.apache.org/jira/browse/CALCITE-3522
https://issues.apache.org/jira/browse/CALCITE-6071
https://issues.apache.org/jira/browse/CALCITE-6210
https://issues.apache.org/jira/browse/CALCITE-6259
https://issues.apache.org/jira/browse/CALCITE-2067
https://issues.apache.org/jira/browse/

[ANNOUNCE] Apache Calcite Avatica 1.25.0 Released

[Francis Chuang]

The Apache Calcite team is pleased to announce the release of Apache
Calcite Avatica 1.25.0.

Avatica is a framework for building database drivers. Avatica defines a
wire API and serialization mechanism for clients to communicate with a
server as a proxy to a database. The reference Avatica client and server
are implemented in Java and communicate over HTTP. Avatica is a
sub-project of Apache Calcite.

Avatica 1.25.0 is a routine release featuring support for JDK 21, Gradle 
8.5 and several bug fixes.


Breaking Change: Due to CALCITE-6282 and CALCITE-6248, illegal dates are 
no longer accepted by casts and time precision will not be ignored when 
returning TIME results, respectively. If you are relying on this 
behavior, your applications may break.


For a full list of changes, please see the release notes:

https://calcite.apache.org/avatica/docs/history.html#v1-25-0

The release is available here:

https://calcite.apache.org/avatica/downloads/avatica.html

We welcome your help and feedback. For more information on how to report
problems and get involved, visit the project website at:

https://calcite.apache.org/avatica/

or the Apache Calcite project website:

https://calcite.apache.org/

Thanks to everyone involved!

Francis Chuang, on behalf of the Apache Calcite team

[ANNOUNCE] Apache Calcite Avatica 1.24.0 Released

[Francis Chuang]

The Apache Calcite team is pleased to announce the release of Apache
Calcite Avatica 1.25.0.

Avatica is a framework for building database drivers. Avatica defines a
wire API and serialization mechanism for clients to communicate with a
server as a proxy to a database. The reference Avatica client and server
are implemented in Java and communicate over HTTP. Avatica is a
sub-project of Apache Calcite.

Avatica 1.25.0 is a routine release featuring support for JDK 21, Gradle 
8.5 and several bug fixes.


Breaking Change: Due to CALCITE-6282 and CALCITE-6248, illegal dates are 
no longer accepted by casts and time precision will not be ignored when 
returning TIME results, respectively. If you are relying on this 
behavior, your applications may break.


For a full list of changes, please see the release notes:

https://calcite.apache.org/avatica/docs/history.html#v1-25-0

The release is available here:

https://calcite.apache.org/avatica/downloads/avatica.html

We welcome your help and feedback. For more information on how to report
problems and get involved, visit the project website at:

https://calcite.apache.org/avatica/

or the Apache Calcite project website:

https://calcite.apache.org/

Thanks to everyone involved!

Francis Chuang, on behalf of the Apache Calcite team

[RESULT] [VOTE] Release Apache Calcite Avatica 1.25.0 (release candidate 0)

[Francis Chuang]

Thanks to everyone who have tested the release candidate and given their 
comments and votes.


The tally is as follows.

6 binding +1s:
Benchao Li
Francis Chuang
Michael Mior
Ruben Quesada Lopez
Sergey Nuyanzin
Stamatis Zampetakis

1 non-binding +1s:
Alessandro Solimando

No 0s or -1s.

Therefore, I am delighted to announce that the proposal to release 
Apache Calcite Avatica 1.25.0 has passed.


Thanks everyone. We’ll now roll the release out to the mirrors.

Francis

Re: [VOTE] Release Apache Calcite Avatica 1.25.0 (release candidate 0)

[Francis Chuang]

Good catch, Ruben and Michael!

I will fix the release notes to say Gradle 8.5 instead of Gradle after 
release.


The gradle wrapper was removed in CALCITE-4575[1] to comply with ASF 
guidelines.


For running tests in docker using docker-compose for releases, I've 
filed CALCITE-6354 to directly use the gradle container to run tests.


Francis

[1] https://issues.apache.org/jira/browse/CALCITE-4575
[2] https://issues.apache.org/jira/browse/CALCITE-6354

On 5/04/2024 3:51 am, Michael Mior wrote:

Francis,

+1 (checked signature and hash, ran tests)

I can't recall if this is expected, but the gradle wrapper is missing from
the release. This means that running tests via docker compose doesn't work.

--
Michael Mior
mm...@apache.org


On Mon, Apr 1, 2024 at 11:40 PM Francis Chuang 
wrote:


Hi all,

I have created a build for Apache Calcite Avatica 1.25.0, release
candidate 0.

Thanks to everyone who has contributed to this release.

You can read the release notes here:

https://github.com/apache/calcite-avatica/blob/avatica-1.25.0-rc0/site/_docs/history.md

The commit to be voted upon:

https://gitbox.apache.org/repos/asf?p=calcite-avatica.git;a=commit;h=62b0fdd3f4e0173d8492eb0e203056f0938dd6f5

Its hash is 62b0fdd3f4e0173d8492eb0e203056f0938dd6f5

Tag:
https://github.com/apache/calcite-avatica/tree/avatica-1.25.0-rc0

The artifacts to be voted on are located here:

https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-1.25.0-rc0

RAT report:

https://gitbox.apache.org/repos/asf/calcite-avatica-site-preview.git/avatica/rat/rat-report.txt

Site preview is here:

https://gitbox.apache.org/repos/asf/calcite-avatica-site-preview.git/avatica/

JavaDoc API preview is here:

https://gitbox.apache.org/repos/asf/calcite-avatica-site-preview.git/avatica/api

The hashes of the artifacts are as follows:

0daa1da33ca0712cb3a4918260081e707c336e06eaacee87962a8ff914f377e8ad21d5fd24490612dbca7d56b83e9d062c39b5cd51701564cf8cba7840ed4806
*apache-calcite-avatica-1.25.0-src.tar.gz

A staged Maven repository is available for review at:

https://repository.apache.org/content/repositories/orgapachecalcite-1223/org/apache/calcite/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/francischuang.asc
https://www.apache.org/dist/calcite/KEYS

To create the jars and test Apache Calcite Avatica: "gradle build
-Prelease -PskipSign".

If you do not have a Java/Gradle environment available, you can run the
tests using docker. To do so, install docker and docker-compose, then
run "docker compose run test" from the root of the directory.

Please vote on releasing this package as Apache Calcite Avatica 1.25.0.

The vote is open for the next 72 hours and passes if a majority of at
least three +1 PMC votes are cast.

[ ] +1 Release this package as Apache Calcite Avatica 1.25.0
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...


Here is my vote:

+1 (binding)

Francis

[jira] [Created] (CALCITE-6354) Use gradle docker container directly when running tests using docker compose

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6354:
---

 Summary: Use gradle docker container directly when running tests 
using docker compose
 Key: CALCITE-6354
 URL: https://issues.apache.org/jira/browse/CALCITE-6354
 Project: Calcite
  Issue Type: Task
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: avatica-1.26.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (CALCITE-6351) Update LICENSE and NOTICE for Jekyll website template

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6351:
---

 Summary: Update LICENSE and NOTICE for Jekyll website template
 Key: CALCITE-6351
 URL: https://issues.apache.org/jira/browse/CALCITE-6351
 Project: Calcite
  Issue Type: Task
  Components: avatica
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: avatica-1.26.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [Follow up] Calcite Setup Issues

[Francis Chuang]

Hi Anurag,

As Mihai said in your previous thread, this is the right list for 
discussing the issues you are encountering.


Please subscribe to the list, so that your emails won't go into the 
moderation queue and to ensure that you're receiving the replies. I am 
sending a copy of this message directly to you, in case you are not 
receiving emails from the list.


Information on subscribing to our lists: 
https://calcite.apache.org/community/#mailing-lists


Docs and tutorials are here: https://calcite.apache.org/docs/

As for the problem you are encountering, please post the exact steps you 
have taken as well as any git repositories you have authored. I am sure 
community members will be able to help.


Francis

On 4/04/2024 4:59 pm, Anurag Naik wrote:

I write this to follow up on a previously sent email regarding the issues I
am facing while trying to build calcite. I need it for a research project
that I am going to be working on. I would like it if you could guide me to
the appropriate communication channels to allow me to interact with the
committers and devs and get the build issues fixed. Also since I am going
to be using calcite for the duration of the research project, I might need
to propose changes to the code as well. Being in contact with the devs
would help that purpose.

Re: [VOTE] Release Apache Calcite Avatica 1.25.0 (release candidate 0)

[Francis Chuang]

Opps, good catch! Please ignore the links to the 
calcite-avatica-site-preview repo. Those are generated by the 
asf-release plugin, but we don't use any preview repos for Calcite.


On 3/04/2024 9:41 pm, Benchao Li wrote:

+1 (binding)

- checked signature and checksum [OK]
- checked copyright year in notice [OK]
- downloaded src, make sure no unexpected files [OK]
- compiled and tested from source [OK]
- reviewed release note [OK]
- checked a few files in Nexus for signature and checksum [OK]
- downloaded javadoc jar, make sure it's in English [OK]

One minor comment is that those gitbox urls seem not valid.

Francis Chuang  于2024年4月2日周二 11:40写道：


Hi all,

I have created a build for Apache Calcite Avatica 1.25.0, release
candidate 0.

Thanks to everyone who has contributed to this release.

You can read the release notes here:
https://github.com/apache/calcite-avatica/blob/avatica-1.25.0-rc0/site/_docs/history.md

The commit to be voted upon:
https://gitbox.apache.org/repos/asf?p=calcite-avatica.git;a=commit;h=62b0fdd3f4e0173d8492eb0e203056f0938dd6f5

Its hash is 62b0fdd3f4e0173d8492eb0e203056f0938dd6f5

Tag:
https://github.com/apache/calcite-avatica/tree/avatica-1.25.0-rc0

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-1.25.0-rc0

RAT report:
https://gitbox.apache.org/repos/asf/calcite-avatica-site-preview.git/avatica/rat/rat-report.txt

Site preview is here:
https://gitbox.apache.org/repos/asf/calcite-avatica-site-preview.git/avatica/

JavaDoc API preview is here:
https://gitbox.apache.org/repos/asf/calcite-avatica-site-preview.git/avatica/api

The hashes of the artifacts are as follows:
0daa1da33ca0712cb3a4918260081e707c336e06eaacee87962a8ff914f377e8ad21d5fd24490612dbca7d56b83e9d062c39b5cd51701564cf8cba7840ed4806
*apache-calcite-avatica-1.25.0-src.tar.gz

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1223/org/apache/calcite/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/francischuang.asc
https://www.apache.org/dist/calcite/KEYS

To create the jars and test Apache Calcite Avatica: "gradle build
-Prelease -PskipSign".

If you do not have a Java/Gradle environment available, you can run the
tests using docker. To do so, install docker and docker-compose, then
run "docker compose run test" from the root of the directory.

Please vote on releasing this package as Apache Calcite Avatica 1.25.0.

The vote is open for the next 72 hours and passes if a majority of at
least three +1 PMC votes are cast.

[ ] +1 Release this package as Apache Calcite Avatica 1.25.0
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...


Here is my vote:

+1 (binding)

Francis

Re: Draft: board report for 2024 Q1

[Francis Chuang]

+1, Great work, Benchao!

On 4/04/2024 5:39 am, Ruben Q L wrote:

+1

Thanks Benchao for preparing the report!


On Wed, Apr 3, 2024 at 7:34 PM Michael Mior  wrote:


+1 Thanks Benchao!

--
Michael Mior
mm...@apache.org


On Wed, Apr 3, 2024 at 6:11 AM Benchao Li  wrote:


Hello,

Below you can find a draft of this quarter's board report. I plan to
submit the final version next Tuesday (Apr 9, 2024).

Please let me know if you have any additions or corrections.

--

Best,
Benchao Li


## 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 (8 years ago)
There are currently 74 committers and 28 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.

Community changes, past quarter:
- Sergey Nuyanzin was added to the PMC on 2024-03-05
- No new committers. Last addition was Hongyu Guo on 2023-11-03.

It's worth mentioning that a few people in Calcite PMC have been
invited as ASF members this year:
- Benchao Li
- Francis Chuang
- Ruben Quesada Lopez
- Sergey Nuyanzin

## Project Activity:
There is no release rolled out in Q1 yet, but we have planned to
release avatica 1.25.0 and calcite 1.37.0 lately.  For now, avatica
1.25.0 RC0 is in voting stage, and calcite 1.37.0 will be kicked off
just after avatica 1.25.0 is released since we have a few co-related
issues for these two versions.

## Community Health:
The community maintains a super healthy status, due to the new
invitation of PMC member, previously it's healthy.

Most of the statistics are steady compared to last quarter, except a
slight decrease for the last three weeks. I assume the reason would be
that we are in the process of calcite 1.37.0 release.It's a little bit
longer than usual, the reason is that we have a few co-related issues
for calcite and avatica, and we need to release avatica before
calcite.

The number of non-committer (contributor) commits per month:
+--+---+-+
| year | month | contributor_commits |
+--+---+-+
| 2024 | 1 |  20 |
| 2024 | 2 |  20 |
| 2024 | 3 |  14 |
+--+---+-+

The number of active reviewers per month:
+--+---+--+
| year | month | active_reviewers |
+--+---+--+
| 2024 | 1 |6 |
| 2024 | 2 |7 |
| 2024 | 3 |6 |
+--+---+--+

Top reviewers in the last 3 months:
+---+-+
| committer | reviews |
+---+-+
| hongyu guo|  15 |
| Mihai Budiu   |  13 |
| Tanner Clary  |  10 |
+---+-+

[VOTE] Release Apache Calcite Avatica 1.25.0 (release candidate 0)

[Francis Chuang]

Hi all,

I have created a build for Apache Calcite Avatica 1.25.0, release
candidate 0.

Thanks to everyone who has contributed to this release.

You can read the release notes here:
https://github.com/apache/calcite-avatica/blob/avatica-1.25.0-rc0/site/_docs/history.md

The commit to be voted upon:
https://gitbox.apache.org/repos/asf?p=calcite-avatica.git;a=commit;h=62b0fdd3f4e0173d8492eb0e203056f0938dd6f5

Its hash is 62b0fdd3f4e0173d8492eb0e203056f0938dd6f5

Tag:
https://github.com/apache/calcite-avatica/tree/avatica-1.25.0-rc0

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-1.25.0-rc0

RAT report:
https://gitbox.apache.org/repos/asf/calcite-avatica-site-preview.git/avatica/rat/rat-report.txt

Site preview is here:
https://gitbox.apache.org/repos/asf/calcite-avatica-site-preview.git/avatica/

JavaDoc API preview is here:
https://gitbox.apache.org/repos/asf/calcite-avatica-site-preview.git/avatica/api

The hashes of the artifacts are as follows:
0daa1da33ca0712cb3a4918260081e707c336e06eaacee87962a8ff914f377e8ad21d5fd24490612dbca7d56b83e9d062c39b5cd51701564cf8cba7840ed4806
*apache-calcite-avatica-1.25.0-src.tar.gz

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1223/org/apache/calcite/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/francischuang.asc
https://www.apache.org/dist/calcite/KEYS

To create the jars and test Apache Calcite Avatica: "gradle build 
-Prelease -PskipSign".


If you do not have a Java/Gradle environment available, you can run the 
tests using docker. To do so, install docker and docker-compose, then 
run "docker compose run test" from the root of the directory.


Please vote on releasing this package as Apache Calcite Avatica 1.25.0.

The vote is open for the next 72 hours and passes if a majority of at
least three +1 PMC votes are cast.

[ ] +1 Release this package as Apache Calcite Avatica 1.25.0
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...


Here is my vote:

+1 (binding)

Francis

Avatica - Main branch closed for 1.25.0 release

[Francis Chuang]

Hey everyone,

Just wanted to drop a quick note that I am closing Avatica's main branch 
to prepare 1.25.0-rc0 for voting.


Francis

Re: Pull Request Reviews for Avatica

[Francis Chuang]

Great work! Thanks, Mihai.

I will have Avatica 1.25.0 rc0 available for voting soon.

On 2/04/2024 4:04 am, Mihai Budiu wrote:

I have merged 6282 and 6248 in Avatica.

Mihai

From: Francis Chuang 
Sent: Monday, March 18, 2024 4:09 AM
To: dev@calcite.apache.org 
Subject: Re: Pull Request Reviews for Avatica

Going through the open PRs again (thanks to community members who
reviewed and merged!), I think these are definitely candidates that can
be merged for the 1.25.0 release:
- CALCITE-6282 - Avatica ignores time precision when returning TIME
results [1]
- CALCITE-6248 - Illegal dates are accepted by casts [2]
- CALCITE-6137 - Upgrade Gradle from 8.1.1 to 8.5, support jdk21 [3]

This one also has some potential as I think there is consensus that's
it's almost ready (with some minor changes):
- CALCITE-5964 - Add test case checking that
connection.getMetaData().getTables() handles responses with different
signature shapes. [4]

These are probably a stretch as there hasn't been consensus yet, but
would be nice to have:
- CALCITE-6135 - BEARER authentication support [5]
- CALCITE-5534 - Add userAgent JDBC param [6]

These 3 are linked together and will probably need a significant amount
of work:
- CALCITE-5535 - Properly truncate time values [7]
- CALCITE-5446 - Add support for TIMESTAMP WITH LOCAL TIME ZONE [8]
- CALCITE-5487 - Proper semantics for TIMESTAMP WITH LOCAL TIME ZONE [9]

Community members, please take a look at the PRs listed and review and
merge if they are ready.

Francis

[1] https://github.com/apache/calcite-avatica/pull/241
[2] https://github.com/apache/calcite-avatica/pull/238
[3] https://github.com/apache/calcite-avatica/pull/234
[4] https://github.com/apache/calcite-avatica/pull/227
[5] https://github.com/apache/calcite-avatica/pull/232
[6] https://github.com/apache/calcite-avatica/pull/211
[7] https://github.com/apache/calcite-avatica/pull/210
[8] https://github.com/apache/calcite-avatica/pull/209
[9] https://github.com/apache/calcite-avatica/pull/205

On 12/03/2024 8:03 am, Francis Chuang wrote:

Going slightly off-topic: I can be RM for the next Avatica release to
make this happen.

Francis

On 12/03/2024 4:38 am, Mihai Budiu wrote:

I haven't spent too much time trying to fix the CI problem, I was
planning to spend some time on this, but this email triggered my
response before I had time to investigate.

I have two PRs outstanding against Avatica which need fixes in both
sides:

Illegal dates are accepted by casts
https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6248
https://github.com/apache/calcite-avatica/pull/238

Avatica ignores time precision when returning TIME results
https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6282
https://github.com/apache/calcite-avatica/pull/241

Mihai


From: Julian Hyde 
Sent: Monday, March 11, 2024 9:49 AM
To: dev@calcite.apache.org 
Subject: Re: Pull Request Reviews for Avatica

Mihai,

Can you list the PRs (jira cases) in this category?

I thought I suggested a solution. disable tests in Calcite based on
the Avatica version number.  And make the changes just before an
Avatica release, and quickly upgrade Calcite, so that any tests you
need to disable aren’t disabled for long.

I’m sure most of the PRs that Francis refers to will not break
Calcite, so there’s no reason to defer those.

Julian


On Mar 11, 2024, at 09:28, Mihai Budiu  wrote:

Some fixes in avatica require simultaneous fixes in Calcite -
sometimes just tests that behave differently. I haven't figured out a
good process that makes both CIs happy.

Mihai

From: Francis Chuang 
Sent: Saturday, March 9, 2024 9:18 PM
To: dev@calcite.apache.org 
Subject: Pull Request Reviews for Avatica

Hey everyone!

Looking at the open pull requests for Avatica [1], it seems that there
are a few that have been languishing for a while.

Some of them seem pretty uncontroversial and simple, but there are some
that will require further discussion (whether through the jira issue or
here on the list).

Can community members please spare some time to review some of the PRs
and commit them?

Francis

[1] https://github.com/apache/calcite-avatica/pulls

Re: Question about exposing tables and columns

[Francis Chuang]

Hey Dilip,

I don't think your attachment made it through, due to moderation. Can 
you try uploading it as a gist on GitHub?


Francis

On 29/03/2024 7:50 am, Dilip Patel wrote:

Hi

We have a data warehouse, and I want to expose only selected tables from 
the DW and create a virtual database. I aim to allow the consumer to 
query these tables via the JDBC driver. I came across the Calcite and 
Avatica libraries and they seem to be capable of doing this.


I was able to connect to the Datawarehouse database and expose all the 
tables and columns using Avatica running as a server. However, despite 
my best efforts, I couldn't find a way to expose only certain tables and 
their columns. Can you provide some examples of how to do this?


I have attached the code. I have implemented custom meta, but I am still 
unable to invoke the getTables function (I believe it is called by the 
Avatica framework itself )


So that you know, the implementation is just rough to get my feet wet 
with Calcite and Avatica.


Thank you,
Dilip

Re: Towards Avatica 1.25.0

[Francis Chuang]

I think the tests for Avatica pull from Calcite master to run, so until 
CALCITE-6282 and CALCITE-6322 are merged in the Calcite repo, the 
Avatica tests will fail.


On 28/03/2024 12:27 am, Mihai Budiu wrote:

I have tried to test these two calcite prs with both versions of avatica 1.23 
and 1.25

From: Istvan Toth 
Sent: Wednesday, March 27, 2024 6:21:59 AM
To: dev@calcite.apache.org 
Subject: Re: Towards Avatica 1.25.0

Which is strange, because AFAIK one of the Avatica tests run by CI is
supposed to run the Calcite test suite with that Avatica build.

On Wed, Mar 27, 2024 at 12:17 PM Istvan Toth  wrote:


Based on my test run above, Calcite tests already fail with Avatica HEAD.
We should figure that out before adding new changes.

On Wed, Mar 27, 2024 at 2:35 AM Mihai Budiu  wrote:


Ok, I have pushed two Calcite PRs that temporarily disable tests, once
these are accepted and merged I hope the Avatica PRs will also pass all
tests.

https://github.com/apache/calcite/pull/3708
https://github.com/apache/calcite/pull/3740

Mihai

From: Francis Chuang 
Sent: Monday, March 25, 2024 9:48 PM
To: dev@calcite.apache.org 
Subject: Re: Towards Avatica 1.25.0

+1 I think this is a good plan

On 26/03/2024 3:25 pm, Mihai Budiu wrote:

Regarding

https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6282

Avatica ignores time precision when returning TIME results

I have PR https://github.com/apache/calcite-avatica/pull/241 in

Avatica, and

a corresponding PR in Calcite

https://github.com/apache/calcite/pull/3740 which disables some tests.


I think that if we merge the Calcite one first, we can then merge the

Avatica one too, since the Avatica CI will succeed. Then as part of the new
Calcite release we mark the Bug.CALCITE_6282 as fixed and re-enable the
disabled tests.


Regarding

https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6248

Illegal dates are accepted by casts

The situation is more complicatred, as I commented in the JIRA case.
I have an Avatica PR https://github.com/apache/calcite-avatica/pull/238.

While this does fix a genuine bug, more changes will be necessary to both
Avatica and Calcite to correctly handle TIME, DATE, and TIMESTAMP
conversions from strings in multiple contexts (literals, casts, values).
(Some of these bugs were fixed in Avatica 1.24, and some new bugs were
seemingly introduced in Avatica 1.24, but Calcite never upgraded to Avatica
1.24, so these bugs were not visible in Calcite.)


I expect we don't plan to fix all these bugs in Avatica 1.25, at least

I don't have time in the next week to work on fixing all of them. So my
proposal is to file a new issue for the remaining bugs that will continue
to exist in Avatica 1.25 (or maybe reuse one of the existing open issues),
and then merge my own PR 238 using a process similar to the one I described
above, using a Bug.CALCITE_6248.If you agree with this plan I will create
update the corresponding PR in Calcite for 6248.


Mihai


From: Francis Chuang 
Sent: Monday, March 25, 2024 5:33 PM
To: dev@calcite.apache.org 
Subject: Re: Towards Avatica 1.25.0

On Avatica's side, we definitely want the tests to pass, otherwise it
will be hard to give the release a +1 during the voting process if there
are test failures.

On 26/03/2024 11:31 am, Mihai Budiu wrote:

Great. I will use this to test the changes on calcite's side. What

needs to happen to merge two prs in avatica? Do we need the avatica CI to
pass our can we temporarily ignore the failures?


If we need the CI to pass it looks like first we have to merge in

calcite main changes which temporarily disable all the tests that cause the
avatica ci to fail.


Mihai

From: Istvan Toth 
Sent: Monday, March 25, 2024 2:14:54 AM
To: Istvan Toth 
Cc: dev@calcite.apache.org 
Subject: Re: Towards Avatica 1.25.0

I could not repro the compilation issue:

My workflow is:

In Avatica:
git checkout main
./gradlew publishToMavenLocal

In Calcite:
git checkout main
./gradlew clean build -Pcalcite.avatica.version=1.25.0-SNAPSHOT
-PenableMavenLocal

The Calcite test suite does fail, but everything compiles.

CalciteSqlOperatorTest > testExtractValue() STANDARD_ERROR
   [Fatal Error] :1:14: The markup in the document following the

root

element must be well-formed.
FAILURE  61.7sec,  492 completed,   3 failed,   1 skipped,
org.apache.calcite.test.CalciteSqlOperatorTest
FAILURE  63.2sec, 8900 completed,   6 failed, 101 skipped, Gradle Test

Run

:core:test

I'm pretty sure that this uses Avatica HEAD, because gradle will fail

early

if I specify a non-existent Avatica version.

Istvan

On Mon, Mar 25, 2024 at 9:52 AM Istvan Toth  wrote:


I have already approved

https://github.com/apache/calcite-avatica/pull/234


If Sergey is not available, any committer (including me) can merge it.

Istvan

On Mon, Mar 25, 2024 at 7:10 AM Mihai Budiu  wrote:

Re: Towards Avatica 1.25.0

[Francis Chuang]

+1 I think this is a good plan

On 26/03/2024 3:25 pm, Mihai Budiu wrote:

Regarding https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6282
Avatica ignores time precision when returning TIME results

I have PR https://github.com/apache/calcite-avatica/pull/241 in Avatica, and
a corresponding PR in Calcite https://github.com/apache/calcite/pull/3740 which 
disables some tests.

I think that if we merge the Calcite one first, we can then merge the Avatica 
one too, since the Avatica CI will succeed. Then as part of the new Calcite 
release we mark the Bug.CALCITE_6282 as fixed and re-enable the disabled tests.

Regarding https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6248
Illegal dates are accepted by casts

The situation is more complicatred, as I commented in the JIRA case.
I have an Avatica PR https://github.com/apache/calcite-avatica/pull/238. While 
this does fix a genuine bug, more changes will be necessary to both Avatica and 
Calcite to correctly handle TIME, DATE, and TIMESTAMP conversions from strings 
in multiple contexts (literals, casts, values). (Some of these bugs were fixed 
in Avatica 1.24, and some new bugs were seemingly introduced in Avatica 1.24, 
but Calcite never upgraded to Avatica 1.24, so these bugs were not visible in 
Calcite.)

I expect we don't plan to fix all these bugs in Avatica 1.25, at least I don't 
have time in the next week to work on fixing all of them. So my proposal is to 
file a new issue for the remaining bugs that will continue to exist in Avatica 
1.25 (or maybe reuse one of the existing open issues), and then merge my own PR 
238 using a process similar to the one I described above, using a 
Bug.CALCITE_6248.If you agree with this plan I will create update the 
corresponding PR in Calcite for 6248.

Mihai


From: Francis Chuang 
Sent: Monday, March 25, 2024 5:33 PM
To: dev@calcite.apache.org 
Subject: Re: Towards Avatica 1.25.0

On Avatica's side, we definitely want the tests to pass, otherwise it
will be hard to give the release a +1 during the voting process if there
are test failures.

On 26/03/2024 11:31 am, Mihai Budiu wrote:

Great. I will use this to test the changes on calcite's side. What needs to 
happen to merge two prs in avatica? Do we need the avatica CI to pass our can 
we temporarily ignore the failures?

If we need the CI to pass it looks like first we have to merge in calcite main 
changes which temporarily disable all the tests that cause the avatica ci to 
fail.

Mihai

From: Istvan Toth 
Sent: Monday, March 25, 2024 2:14:54 AM
To: Istvan Toth 
Cc: dev@calcite.apache.org 
Subject: Re: Towards Avatica 1.25.0

I could not repro the compilation issue:

My workflow is:

In Avatica:
git checkout main
./gradlew publishToMavenLocal

In Calcite:
git checkout main
./gradlew clean build -Pcalcite.avatica.version=1.25.0-SNAPSHOT
-PenableMavenLocal

The Calcite test suite does fail, but everything compiles.

CalciteSqlOperatorTest > testExtractValue() STANDARD_ERROR
  [Fatal Error] :1:14: The markup in the document following the root
element must be well-formed.
FAILURE  61.7sec,  492 completed,   3 failed,   1 skipped,
org.apache.calcite.test.CalciteSqlOperatorTest
FAILURE  63.2sec, 8900 completed,   6 failed, 101 skipped, Gradle Test Run
:core:test

I'm pretty sure that this uses Avatica HEAD, because gradle will fail early
if I specify a non-existent Avatica version.

Istvan

On Mon, Mar 25, 2024 at 9:52 AM Istvan Toth  wrote:


I have already approved https://github.com/apache/calcite-avatica/pull/234

If Sergey is not available, any committer (including me) can merge it.

Istvan

On Mon, Mar 25, 2024 at 7:10 AM Mihai Budiu  wrote:


I have authored the first two PRs in this list, they are certainly ready
on the Avatica side, and they have been approved and are ready to merge.

I have made corresponding PR on the Calcite side, and
I have been trying to test them with Calcite, but it's not easy.

First, there is a flag in Calcite called localAvatica, which is supposed
to build using the a version of Avatica on the local disk. That doesn't
work, because seemingly some packages have to be updated, including gradle.

I have tried replacing the avatica-core and avatica-server jars in the
gradle build files with local versions. But Calcite still doesn't build:
some APIs have changed in Avatica, and Calcite will not build with the new
APIs. In particular, the Avatica server Main class seems to require
different argument types.

Maybe there are other problems as well, but I got blocked on these.

Is it OK to merge the PRs in Avatica if the Avatica CI fails? The CI
fails because one of the tasks is to test the Calcite core, and clearly
that will fail until Calcite itself is upgraded.

I could disable the failing tests in Calcite core temporarily, but I
suspect other Calcite projects will fail, which are not being tested with
Avatica's CI.

I appreciate any h

Re: Towards Avatica 1.25.0

[Francis Chuang]

On Avatica's side, we definitely want the tests to pass, otherwise it 
will be hard to give the release a +1 during the voting process if there 
are test failures.


On 26/03/2024 11:31 am, Mihai Budiu wrote:

Great. I will use this to test the changes on calcite's side. What needs to 
happen to merge two prs in avatica? Do we need the avatica CI to pass our can 
we temporarily ignore the failures?

If we need the CI to pass it looks like first we have to merge in calcite main 
changes which temporarily disable all the tests that cause the avatica ci to 
fail.

Mihai

From: Istvan Toth 
Sent: Monday, March 25, 2024 2:14:54 AM
To: Istvan Toth 
Cc: dev@calcite.apache.org 
Subject: Re: Towards Avatica 1.25.0

I could not repro the compilation issue:

My workflow is:

In Avatica:
git checkout main
./gradlew publishToMavenLocal

In Calcite:
git checkout main
./gradlew clean build -Pcalcite.avatica.version=1.25.0-SNAPSHOT
-PenableMavenLocal

The Calcite test suite does fail, but everything compiles.

CalciteSqlOperatorTest > testExtractValue() STANDARD_ERROR
 [Fatal Error] :1:14: The markup in the document following the root
element must be well-formed.
FAILURE  61.7sec,  492 completed,   3 failed,   1 skipped,
org.apache.calcite.test.CalciteSqlOperatorTest
FAILURE  63.2sec, 8900 completed,   6 failed, 101 skipped, Gradle Test Run
:core:test

I'm pretty sure that this uses Avatica HEAD, because gradle will fail early
if I specify a non-existent Avatica version.

Istvan

On Mon, Mar 25, 2024 at 9:52 AM Istvan Toth  wrote:


I have already approved https://github.com/apache/calcite-avatica/pull/234

If Sergey is not available, any committer (including me) can merge it.

Istvan

On Mon, Mar 25, 2024 at 7:10 AM Mihai Budiu  wrote:


I have authored the first two PRs in this list, they are certainly ready
on the Avatica side, and they have been approved and are ready to merge.

I have made corresponding PR on the Calcite side, and
I have been trying to test them with Calcite, but it's not easy.

First, there is a flag in Calcite called localAvatica, which is supposed
to build using the a version of Avatica on the local disk. That doesn't
work, because seemingly some packages have to be updated, including gradle.

I have tried replacing the avatica-core and avatica-server jars in the
gradle build files with local versions. But Calcite still doesn't build:
some APIs have changed in Avatica, and Calcite will not build with the new
APIs. In particular, the Avatica server Main class seems to require
different argument types.

Maybe there are other problems as well, but I got blocked on these.

Is it OK to merge the PRs in Avatica if the Avatica CI fails? The CI
fails because one of the tasks is to test the Calcite core, and clearly
that will fail until Calcite itself is upgraded.

I could disable the failing tests in Calcite core temporarily, but I
suspect other Calcite projects will fail, which are not being tested with
Avatica's CI.

I appreciate any help.
Mihai


From: Francis Chuang 
Sent: Sunday, March 24, 2024 10:59 PM
To: dev@calcite.apache.org 
Subject: Towards Avatica 1.25.0

Hey everyone,

I want to start the discussion for releasing Avatica 1.25.0 before we
release Calcite 1.37.0.

Relevant discussions are here:
- Calcite 1.37.0:
https://lists.apache.org/thread/k27rwmhggmsbvwmgxs9fydcw2f0hook8
- Avatica PRs:
https://lists.apache.org/list?dev@calcite.apache.org:lte=1M:avatica

I think it would be a good idea to get these PRs in for the release:
- https://github.com/apache/calcite-avatica/pull/241
- https://github.com/apache/calcite-avatica/pull/238
- https://github.com/apache/calcite-avatica/pull/234

Community members, please take a look at those PRs and leave your
reviews if necessary. If possible, please consider merging as well.

I hope to make rc0 available for voting end of this week or early next
week. Does this schedule suit?

Francis

[jira] [Created] (CALCITE-6339) Replace hashicorp/go-uuid with google/uuid

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6339:
---

 Summary: Replace hashicorp/go-uuid with google/uuid
 Key: CALCITE-6339
 URL: https://issues.apache.org/jira/browse/CALCITE-6339
 Project: Calcite
  Issue Type: Task
  Components: avatica-go
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: avatica-go-5.4.0


The hashicorp/uuid library generates strings that look like uuids but are 
purely random. It is also not as popular or as active as the google/uuid 
library.

The google/uuid library generates real uuids that are RFC compliant. The 
library is also more popular and actively maintained.

These ids are used to generate connection ids, so whether they are RFC 
compliant or not is inconsequential, however, it is a good idea to generate 
compliant uuids if downstream users behind avatica expects correct and 
compliant uuids.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Towards Avatica 1.25.0

[Francis Chuang]

Hey everyone,

I want to start the discussion for releasing Avatica 1.25.0 before we 
release Calcite 1.37.0.


Relevant discussions are here:
- Calcite 1.37.0: 
https://lists.apache.org/thread/k27rwmhggmsbvwmgxs9fydcw2f0hook8
- Avatica PRs: 
https://lists.apache.org/list?dev@calcite.apache.org:lte=1M:avatica


I think it would be a good idea to get these PRs in for the release:
- https://github.com/apache/calcite-avatica/pull/241
- https://github.com/apache/calcite-avatica/pull/238
- https://github.com/apache/calcite-avatica/pull/234

Community members, please take a look at those PRs and leave your 
reviews if necessary. If possible, please consider merging as well.


I hope to make rc0 available for voting end of this week or early next 
week. Does this schedule suit?


Francis

Re: Pull Request Reviews for Avatica

[Francis Chuang]

Going through the open PRs again (thanks to community members who 
reviewed and merged!), I think these are definitely candidates that can 
be merged for the 1.25.0 release:
- CALCITE-6282 - Avatica ignores time precision when returning TIME 
results [1]

- CALCITE-6248 - Illegal dates are accepted by casts [2]
- CALCITE-6137 - Upgrade Gradle from 8.1.1 to 8.5, support jdk21 [3]

This one also has some potential as I think there is consensus that's 
it's almost ready (with some minor changes):
- CALCITE-5964 - Add test case checking that 
connection.getMetaData().getTables() handles responses with different 
signature shapes. [4]


These are probably a stretch as there hasn't been consensus yet, but 
would be nice to have:

- CALCITE-6135 - BEARER authentication support [5]
- CALCITE-5534 - Add userAgent JDBC param [6]

These 3 are linked together and will probably need a significant amount 
of work:

- CALCITE-5535 - Properly truncate time values [7]
- CALCITE-5446 - Add support for TIMESTAMP WITH LOCAL TIME ZONE [8]
- CALCITE-5487 - Proper semantics for TIMESTAMP WITH LOCAL TIME ZONE [9]

Community members, please take a look at the PRs listed and review and 
merge if they are ready.


Francis

[1] https://github.com/apache/calcite-avatica/pull/241
[2] https://github.com/apache/calcite-avatica/pull/238
[3] https://github.com/apache/calcite-avatica/pull/234
[4] https://github.com/apache/calcite-avatica/pull/227
[5] https://github.com/apache/calcite-avatica/pull/232
[6] https://github.com/apache/calcite-avatica/pull/211
[7] https://github.com/apache/calcite-avatica/pull/210
[8] https://github.com/apache/calcite-avatica/pull/209
[9] https://github.com/apache/calcite-avatica/pull/205

On 12/03/2024 8:03 am, Francis Chuang wrote:
Going slightly off-topic: I can be RM for the next Avatica release to 
make this happen.


Francis

On 12/03/2024 4:38 am, Mihai Budiu wrote:
I haven't spent too much time trying to fix the CI problem, I was 
planning to spend some time on this, but this email triggered my 
response before I had time to investigate.


I have two PRs outstanding against Avatica which need fixes in both 
sides:


Illegal dates are accepted by casts
https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6248
https://github.com/apache/calcite-avatica/pull/238

Avatica ignores time precision when returning TIME results
https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6282
https://github.com/apache/calcite-avatica/pull/241

Mihai


From: Julian Hyde 
Sent: Monday, March 11, 2024 9:49 AM
To: dev@calcite.apache.org 
Subject: Re: Pull Request Reviews for Avatica

Mihai,

Can you list the PRs (jira cases) in this category?

I thought I suggested a solution. disable tests in Calcite based on 
the Avatica version number.  And make the changes just before an 
Avatica release, and quickly upgrade Calcite, so that any tests you 
need to disable aren’t disabled for long.


I’m sure most of the PRs that Francis refers to will not break 
Calcite, so there’s no reason to defer those.


Julian


On Mar 11, 2024, at 09:28, Mihai Budiu  wrote:

Some fixes in avatica require simultaneous fixes in Calcite - 
sometimes just tests that behave differently. I haven't figured out a 
good process that makes both CIs happy.


Mihai

From: Francis Chuang 
Sent: Saturday, March 9, 2024 9:18 PM
To: dev@calcite.apache.org 
Subject: Pull Request Reviews for Avatica

Hey everyone!

Looking at the open pull requests for Avatica [1], it seems that there
are a few that have been languishing for a while.

Some of them seem pretty uncontroversial and simple, but there are some
that will require further discussion (whether through the jira issue or
here on the list).

Can community members please spare some time to review some of the PRs
and commit them?

Francis

[1] https://github.com/apache/calcite-avatica/pulls

[jira] [Created] (CALCITE-6334) Release Avatica 1.25.0

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6334:
---

 Summary: Release Avatica 1.25.0
 Key: CALCITE-6334
 URL: https://issues.apache.org/jira/browse/CALCITE-6334
 Project: Calcite
  Issue Type: Task
Reporter: Francis Chuang
Assignee: Francis Chuang






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Towards Calcite 1.37.0

[Francis Chuang]

Hey everyone,

I just wanted to jump in regarding CALCITE-6248 [1] and CALCITE-6282 (no 
corresponding PRs in the Calcite repo yet).


The corresponding PRs in the Avatica repo are:
- https://github.com/apache/calcite-avatica/pull/238
- https://github.com/apache/calcite-avatica/pull/241

As the issue will require changes to both Calcite and Avatica in a 
coordinated fashion, what do you guys think about releasing Avatica 
1.25.0 first? I can be RM for the Avatica release.


Mihai, can you please confirm if this approach works for you?

Discussion for getting changes simultaneously into both Avatica and 
Calcite is here [2].


Francis

[1] https://github.com/apache/calcite/pull/3708
[2] https://lists.apache.org/thread/5w3ry3zbm7671ffp4pxh7lx6cgc5r3tq

On 13/03/2024 10:07 pm, Benchao Li wrote:

Thank you, Hongyu, for volunteering to be a release manager.

What's worth to mention is that to be a release manager does not
require PMC membership nor being a committer, and it is a good chance
to be involved in community activities apart from code/discussion,
which would be a good additional credit for being considered as
committer or PMC member candidate.

Hongyu Guo  于2024年3月13日周三 11:29写道：


I would like to take on the role of RM for one release

On Thu, Mar 7, 2024 at 2:58 AM Alessandro Solimando <
alessandro.solima...@gmail.com> wrote:


Hey Sergey,
thanks for being the release manager for 1.37.0.

I have added fixVersion=1.37.0 to CALCITE-2040
, as its associated PR
 is in good shape IMO, and we
are trying to get it done shortly with Hongyu.

Best regards,
Alessandro

On Wed, 6 Mar 2024 at 16:49, Sergey Nuyanzin  wrote:


Updates about 1.37.0 releasing

According to our Jira dashboard [1] and Github [2], there
are 17 pending issues that could / should be part of the release.
I'd propose to make a collective effort to try to clean up our 1.37.0
backlog and merge the PRs which are in a good state. I'd propose to
aim for about 2 weeks to release 1.37.0, this will give us about
some time to clean up pending PRs for the next version. What do you

think?


And contributors, if you have any work that is in good shape and want
to be included in 1.37.0, please mark the fixVersion to 1.37.0, this
will inform the release manager, and we'll try our best to get it in.

A quick update on the current status for issues targeted 1.37.0
We need more reviewers for #2

#1. Issues already have reviewers, and seems promising to be merged

shortly

https://issues.apache.org/jira/browse/CALCITE-6138
https://issues.apache.org/jira/browse/CALCITE-6015
https://issues.apache.org/jira/browse/CALCITE-6283
https://issues.apache.org/jira/browse/CALCITE-5607

  #2. Issues has been reviewed, and needs another reviewer
https://issues.apache.org/jira/browse/CALCITE-3522
https://issues.apache.org/jira/browse/CALCITE-6071
https://issues.apache.org/jira/browse/CALCITE-6210
https://issues.apache.org/jira/browse/CALCITE-6259
https://issues.apache.org/jira/browse/CALCITE-2067
https://issues.apache.org/jira/browse/CALCITE-6226
https://issues.apache.org/jira/browse/CALCITE-6193


It could happen that I miss something, please let me know
if there is something with fixVersion 1.37.0 ready for review and not
mentioned here

Also I created a JIRA issue for releasing 1.37.0
https://issues.apache.org/jira/browse/CALCITE-6302

[1]


https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950

[2] https://github.com/apache/calcite/pulls

On Fri, Feb 23, 2024 at 9:24 PM Julian Hyde 
wrote:


+1 for a release.

Our users rely on a regular cadence of releases. If someone submits a
patch and doesn’t see it in a release until 6 months later (or it sits
un-reviewed) they will be less inclined to submit a patch.

Yeah, I know Open Source Doesn’t Require Providing Builds [1] but it

makes

everyone’s life easier.

Julian

[1] https://news.ycombinator.com/item?id=39094387



On Feb 21, 2024, at 1:18 AM, Stamatis Zampetakis 

wrote:


With so many commits it's definitely a good time to cut a new

release.


I can be the RM for 1.39.0 or 1.40.0 depending on the timing.

Best,
Stamatis

On Wed, Feb 21, 2024 at 12:10 AM Sergey Nuyanzin <

snuyan...@gmail.com>

wrote:


Thanks for starting the discussion


@Sergey, are you still available for being the release manager for

1.37.0?


I think so, in theory I could start with some steps in one/two weeks

if

there is no objections



On Mon, Feb 19, 2024 at 12:29 PM Benchao Li 

wrote:



It's been a bit more than 3 months since our last release

(2023-11-10)

[1] and there are currently 100+ new commits in main branch. Per

our

tradition of producing one release every 2-3 months, I think it's

time

to consider for next release now.

According to [2], the following release managers would be:
- 1.37.0 Sergey Nuyanzin
- 1.38.0 Julian Hyde

@Sergey, are you still available for being the release manager for

1.37.0?

Re: Pull Request Reviews for Avatica

[Francis Chuang]

Going slightly off-topic: I can be RM for the next Avatica release to 
make this happen.


Francis

On 12/03/2024 4:38 am, Mihai Budiu wrote:

I haven't spent too much time trying to fix the CI problem, I was planning to 
spend some time on this, but this email triggered my response before I had time 
to investigate.

I have two PRs outstanding against Avatica which need fixes in both sides:

Illegal dates are accepted by casts
https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6248
https://github.com/apache/calcite-avatica/pull/238

Avatica ignores time precision when returning TIME results
https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6282
https://github.com/apache/calcite-avatica/pull/241

Mihai


From: Julian Hyde 
Sent: Monday, March 11, 2024 9:49 AM
To: dev@calcite.apache.org 
Subject: Re: Pull Request Reviews for Avatica

Mihai,

Can you list the PRs (jira cases) in this category?

I thought I suggested a solution. disable tests in Calcite based on the Avatica 
version number.  And make the changes just before an Avatica release, and 
quickly upgrade Calcite, so that any tests you need to disable aren’t disabled 
for long.

I’m sure most of the PRs that Francis refers to will not break Calcite, so 
there’s no reason to defer those.

Julian


On Mar 11, 2024, at 09:28, Mihai Budiu  wrote:

Some fixes in avatica require simultaneous fixes in Calcite - sometimes just 
tests that behave differently. I haven't figured out a good process that makes 
both CIs happy.

Mihai

From: Francis Chuang 
Sent: Saturday, March 9, 2024 9:18 PM
To: dev@calcite.apache.org 
Subject: Pull Request Reviews for Avatica

Hey everyone!

Looking at the open pull requests for Avatica [1], it seems that there
are a few that have been languishing for a while.

Some of them seem pretty uncontroversial and simple, but there are some
that will require further discussion (whether through the jira issue or
here on the list).

Can community members please spare some time to review some of the PRs
and commit them?

Francis

[1] https://github.com/apache/calcite-avatica/pulls

Pull Request Reviews for Avatica

[Francis Chuang]

Hey everyone!

Looking at the open pull requests for Avatica [1], it seems that there 
are a few that have been languishing for a while.


Some of them seem pretty uncontroversial and simple, but there are some 
that will require further discussion (whether through the jira issue or 
here on the list).


Can community members please spare some time to review some of the PRs 
and commit them?


Francis

[1] https://github.com/apache/calcite-avatica/pulls

Re: [ANNOUNCE] Sergey Nuyanzin joins Calcite PMC

[Francis Chuang]

Congratulations, Sergey!

On 6/03/2024 5:59 am, Ruben Q L wrote:

Congratulations Sergey!


On Tue, Mar 5, 2024 at 6:48 PM Tanner Clary 
wrote:


Congrats Sergey!

Tanner

On Tue, Mar 5, 2024 at 4:14 AM Benchao Li  wrote:


I am pleased to announce that Sergey has accepted an invitation to
join the Calcite PMC. Sergey has been a consistent and helpful figure
in the Calcite community for which we are very grateful. We look
forward to the continued contributions and support.

Please join me in congratulating Sergey!

Benchao (on behalf of the Calcite PMC)

Re: Thesis question regarding Calcite placement in taxonomy

[Francis Chuang]

Hello Teun,

It seems your attachment didn't come through. Can you upload it to imgr 
and link it here?


Thanks,
Francis

On 29/01/2024 6:45 pm, Teun Mathijssen wrote:

Hi all,

I'm currently writing my Master's thesis in Software Engineering on 
Apache Calcite. For my background research I want to classify Calcite 
under a taxonomy formulated in "Enabling Query Processing across 
Heterogeneous Data Models: A Survey" 
(https://ieeexplore.ieee.org/abstract/document/8258302 
). The authors of 
this paper classify federated datastores from available literature under 
the data type and query interfaces they support. I made a visualization 
of their taxonomy which can be found in the attached file.


My question to you is: under which of these classes can we put Calcite? 
I think Calcite is a multistore system (with the sidenote that it does 
not manage its own data) as it provides one SQL interface and it's 
capable of handling heterogeneous data. What do you think? Can we even 
categorize it?


Looking forward to your answer.

Kind regards,

Teun Mathijssen

Re: Draft: board report for 2023 Q4

[Francis Chuang]

+1, Thanks, Benchao!

On 9/01/2024 2:22 am, Julian Hyde wrote:

Looks good. Thanks, Benchao!

Julian


On Jan 8, 2024, at 00:33, Ruben Q L  wrote:

+1
Thanks Benchao for preparing this report!



On Fri, Jan 5, 2024 at 1:46 PM Stamatis Zampetakis 
wrote:

Looks good thanks for putting it together Benchao!


On Fri, Jan 5, 2024 at 2:41 PM Benchao Li  wrote:

Hello,

Below you can find a draft of this quarter's board report. I plan to
submit the final version next Tuesday (Jan 9, 2024).

Please let me know if you have any additions or corrections.

Best,
Benchao Li
---

## 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 (8 years ago)
There are currently 74 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.

Community changes, past quarter:
- No new PMC members. Last addition was Benchao Li on 2023-01-27.
- Hongyu Guo was added as committer on 2023-11-03
- Runkang He was added as committer on 2023-11-03
- Lei Shen was added as committer on 2023-11-01
- Mihai Budiu was added as committer on 2023-10-26
- Ran Tao was added as committer on 2023-10-28

Following our yearly rotation tradition, the PMC has elected a new
chair: Benchao Li.

## Project Activity:
Apache Calcite 1.36.0 was released on 2023-11-10. It contains
contributions from 30 contributors, and resolves 125 issues.  The new
release adds 30 new SQL functions in various libraries such as
BigQuery and Spark, contains many improvements hardening TABLESAMPLE,
integrates SQL Logic Test suite, and many more core improvements such
as the support of recursive WITH and CREATE TABLE ... LIKE DDL.

Apache Calcite Avatica 1.24.0 was released on 2023-12-04. It features
mostly dependency upgrades with some minor bug fixes and features, and
contains a breaking change: due to CALCITE-5678, date literals not
satisfying the Gregorian calendar will be rejected.

Apache Calcite Avatica Go 5.3.0 was released on 2023-12-11. It is a
maintenance release of Avatica Go including dependency updates and bug
fixes. This release supports Go 1.20 and 1.21, which are currently the
versions supported and maintained by the Go team.

## Community Health:
The community maintains a healthy status.

Mailing list and JIRA activity has slightly dropped (dev@ -4%, issues@
-36%, JIRA opened -47%, JIRA closed -33%) due to the holiday of
Chrismas and New Year. However, commit (+52%) and PRs closed(+27%) has
increased on the contrary, one reason is we have many commits/PRs
testing the unstable test problem in CALCITE-6123, another reason is
some new contributors are used to opening and closeing the PR
repeatedly.

The number of non-committer (contributor) commits per month:
+--+---+-+
| year | month | contributor_commits |
+--+---+-+
| 2023 |10 |  35 |
| 2023 |11 |  21 |
| 2023 |12 |  13 |
+--+---+-+

The number of active reviewers per month:
+--+---+--+
| year | month | active_reviewers |
+--+---+--+
| 2023 |10 |8 |
| 2023 |11 |   12 |
| 2023 |12 |6 |
+--+---+--+

Top reviewers in the last 3 months:
+--+-+
| committer| reviews |
+--+-+
| Jiajun  |  11 |
| Julian Hyde|  11 |
| Mihai Budiu  |   9 |
+--+-+


The number of non-committer commits and active reviewers are slightly
decreased compared to Q3 due to the holidays, but the number is still
very good compared to times before 2023 Q2.

Re: [ANNOUNCE] New Calcite PMC chair: Benchao Li

[Francis Chuang]

Congratulations, Benchao!

On 21/12/2023 8:24 pm, Guangdong Liu wrote:

Congratulations!

--

Best Regards



Liugddx
liug...@gmail.com


Stamatis Zampetakis  于2023年12月21日周四 17:18写道：


Calcite community members,

I am pleased to announce that we have a new PMC chair and VP as per
our tradition of rotating the chair once a year. I have resigned, and
Benchao Li was duly elected by the PMC and approved unanimously by the
Board.

Please join me in congratulating Benchao!

Best regards,
Stamatis

[ANNOUNCE] Apache Calcite Avatica Go 5.3.0 released

[Francis Chuang]

The Apache Calcite team is pleased to announce the release of Apache
Calcite Avatica Go 5.3.0.

Avatica is a framework for building database drivers. Avatica
defines a wire API and serialization mechanism for clients to
communicate with a server as a proxy to a database. The reference
Avatica client and server are implemented in Java and communicate
over HTTP. Avatica is a sub-project of Apache Calcite.

The Avatica Go client is a Go database/sql driver that enables Go
programs to communicate with the Avatica server.

Apache Calcite Avatica Go 5.3.0 is a maintenance release of Avatica Go 
including dependency updates and bug fixes. This release supports Go 
1.20 and 1.21, which are currently the versions supported and maintained 
by the Go team.


For more information, please see the release notes:

https://calcite.apache.org/avatica/docs/go_history.html#v5-3-0

The release is available here:

https://calcite.apache.org/avatica/downloads/avatica-go.html

We welcome your help and feedback. For more information on how to
report problems, and to get involved, visit the project website at

https://calcite.apache.org/avatica

Francis Chuang, on behalf of the Apache Calcite Team

[RESULT] [VOTE] Release apache-calcite-avatica-go-5.3.0 (release candidate 0)

[Francis Chuang]

Thanks to everyone who has tested the release candidate and given
their comments and votes.

The tally is as follows.

3 binding +1s:
Benchao Li
Francis Chuang
Stamatis Zampetakis

1 non-binding +1s:
Sergey Nuyanzin

No 0s or -1s.

Therefore I am delighted to announce that the proposal to release
Apache Calcite Avatica Go 5.3.0 has passed.

Thanks everyone. We’ll now roll the release out to the mirrors.
Francis

Re: squashing commit already in upstream

[Francis Chuang]

As your 2 commits are the first 2 commits on main, I think it's okay if 
you go ahead and squash them. Since they were committed on the weekend, 
I don't think too many people would have updated their main branch.


Francis

On 11/12/2023 8:20 am, Mihai Budiu wrote:

Hello,

By mistake I merged a PR which contained two commits instead of the customary 
one. What is the policy (and method) for fixing this for the Calcite repository?

https://github.com/apache/calcite/commit/5b441c639de1ec428891061b931bd69d9996efe4

Should have been squashed into

https://github.com/apache/calcite/commit/1b36f07ce98f0e6d620b5ea1e1c773b376c3e81e

Sorry for the complications, I will double check next time.

Thank you,
Mihai

Re: [VOTE] Release apache-calcite-avatica-go-5.3.0 (release candidate 0)

[Francis Chuang]

Hey everyone,

The vote for Avatica-Go 5.3.0 is still open. Please test and vote for 
rc0, so that we can release this.


Thank you,
Francis

On 4/12/2023 3:18 pm, Francis Chuang wrote:

Hi all,

I have created a release for Apache Calcite Avatica Go 5.3.0, release 
candidate 0.


Thanks to everyone who has contributed to this release. The release 
notes are available here:

https://github.com/apache/calcite-avatica-go/blob/v5.3.0-rc0/site/_docs/go_history.md

The commit to be voted on:
https://gitbox.apache.org/repos/asf?p=calcite-avatica-go.git;a=commit;h=8657d0ac4148dca20f67253e78be222d10cc9c6a

The hash is 8657d0ac4148dca20f67253e78be222d10cc9c6a

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-go-5.3.0-rc0/

The hashes of the artifacts are as follows:
src.tar.gz 4927DE62 7C46BE04 2F8092E6 86D5FE36 A3E0115F 7D1672AB 
F0B32285 AB437FE53B6347CE 5824E1D9 C37A24D0 8B80088C 132F706D D484F0F8 
C2961453 941AC048


Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/francischuang.asc

Instructions for running the test suite is located here:
https://github.com/apache/calcite-avatica-go/blob/v5.3.0-rc0/site/develop/avatica-go.md#testing

Please vote on releasing this package as Apache Calcite Avatica Go 5.3.0.

To run the tests without a Go environment, install docker and docker 
compose. Then, in the root of the release's directory, run: docker 
compose run test


When the test suite completes, run "docker compose down" to remove and 
shutdown all the containers.


The vote is open for the next 72 hours and passes if a majority of at 
least three +1 PMC votes are cast.


[ ] +1 Release this package as Apache Calcite Avatica Go 5.3.0
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...


Here is my vote:

+1 (binding)

Francis

[VOTE] Release apache-calcite-avatica-go-5.3.0 (release candidate 0)

[Francis Chuang]

Hi all,

I have created a release for Apache Calcite Avatica Go 5.3.0, release 
candidate 0.


Thanks to everyone who has contributed to this release. The release 
notes are available here:

https://github.com/apache/calcite-avatica-go/blob/v5.3.0-rc0/site/_docs/go_history.md

The commit to be voted on:
https://gitbox.apache.org/repos/asf?p=calcite-avatica-go.git;a=commit;h=8657d0ac4148dca20f67253e78be222d10cc9c6a

The hash is 8657d0ac4148dca20f67253e78be222d10cc9c6a

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-go-5.3.0-rc0/

The hashes of the artifacts are as follows:
src.tar.gz 4927DE62 7C46BE04 2F8092E6 86D5FE36 A3E0115F 7D1672AB 
F0B32285 AB437FE53B6347CE 5824E1D9 C37A24D0 8B80088C 132F706D D484F0F8 
C2961453 941AC048


Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/francischuang.asc

Instructions for running the test suite is located here:
https://github.com/apache/calcite-avatica-go/blob/v5.3.0-rc0/site/develop/avatica-go.md#testing

Please vote on releasing this package as Apache Calcite Avatica Go 5.3.0.

To run the tests without a Go environment, install docker and docker 
compose. Then, in the root of the release's directory, run: docker 
compose run test


When the test suite completes, run "docker compose down" to remove and 
shutdown all the containers.


The vote is open for the next 72 hours and passes if a majority of at 
least three +1 PMC votes are cast.


[ ] +1 Release this package as Apache Calcite Avatica Go 5.3.0
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...


Here is my vote:

+1 (binding)

Francis

[jira] [Created] (CALCITE-6155) Add additional rel/ tag to avatica-go release script

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6155:
---

 Summary: Add additional rel/ tag to avatica-go release script
 Key: CALCITE-6155
 URL: https://issues.apache.org/jira/browse/CALCITE-6155
 Project: Calcite
  Issue Type: New Feature
  Components: avatica-go
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: avatica-go-5.3.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (CALCITE-6154) Upgrade protobuf library to 1.31.0

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6154:
---

 Summary: Upgrade protobuf library to 1.31.0
 Key: CALCITE-6154
 URL: https://issues.apache.org/jira/browse/CALCITE-6154
 Project: Calcite
  Issue Type: New Feature
  Components: avatica-go
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: avatica-go-5.3.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (CALCITE-6153) Recompile protobuf messages to Avatica 1.24

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6153:
---

 Summary: Recompile protobuf messages to Avatica 1.24
 Key: CALCITE-6153
 URL: https://issues.apache.org/jira/browse/CALCITE-6153
 Project: Calcite
  Issue Type: New Feature
  Components: avatica-go
Affects Versions: avatica-go-5.3.0
Reporter: Francis Chuang
Assignee: Francis Chuang






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (CALCITE-6152) Test against Avatica 1.24.0

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6152:
---

 Summary: Test against Avatica 1.24.0
 Key: CALCITE-6152
 URL: https://issues.apache.org/jira/browse/CALCITE-6152
 Project: Calcite
  Issue Type: New Feature
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: avatica-go-5.3.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (CALCITE-6151) Test against Go 1.20 and 1.21

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6151:
---

 Summary: Test against Go 1.20 and 1.21
 Key: CALCITE-6151
 URL: https://issues.apache.org/jira/browse/CALCITE-6151
 Project: Calcite
  Issue Type: New Feature
  Components: avatica-go
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: avatica-go-5.3.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[ANNOUNCE] Apache Calcite Avatica 1.24.0 Released

[Francis Chuang]

The Apache Calcite team is pleased to announce the release of Apache
Calcite Avatica 1.24.0.

Avatica is a framework for building database drivers. Avatica defines a
wire API and serialization mechanism for clients to communicate with a
server as a proxy to a database. The reference Avatica client and server
are implemented in Java and communicate over HTTP. Avatica is a
sub-project of Apache Calcite.

Apache Calcite Avatica 1.24.0 features mostly dependency upgrades with 
some minor bug fixes and features. Of note is the breaking change 
introduced in CALCITE-5675 where date literals not satisfying the 
Gregorian calendar will be rejected.


For a full list of changes, please see the release notes:

https://calcite.apache.org/avatica/docs/history.html#v1-24-0

The release is available here:

https://calcite.apache.org/avatica/downloads/avatica.html

We welcome your help and feedback. For more information on how to report
problems and get involved, visit the project website at:

https://calcite.apache.org/avatica/

or the Apache Calcite project website:

https://calcite.apache.org/

Thanks to everyone involved!

Francis Chuang, on behalf of the Apache Calcite team

[RESULT] [VOTE] Release Apache Calcite Avatica 1.24.0 (release candidate 1)

[Francis Chuang]

Thanks to everyone who has tested the release candidate and given
their comments and votes.

The tally is as follows.

3 binding +1s:
Benchao Li
Francis Chuang
Stamatis Zampetakis

1 non-binding +1s:
Istvan Toth

No 0s or -1s.

Therefore I am delighted to announce that the proposal to release
Apache Calcite Avatica 1.24.0 has passed.

Thanks everyone. We’ll now roll the release out to the mirrors.
Francis

[VOTE] Release Apache Calcite Avatica 1.24.0 (release candidate 1)

[Francis Chuang]

Hi all,

I have created a build for Apache Calcite Avatica 1.24.0, release
candidate 1.

Thanks to everyone who has contributed to this release.

You can read the release notes here:
https://github.com/apache/calcite-avatica/blob/avatica-1.24.0-rc1/site/_docs/history.md

The commit to be voted upon:
https://gitbox.apache.org/repos/asf?p=calcite-avatica.git;a=commit;h=4c0999ba154915eee201bd7a037e223e9368a97d

Its hash is 4c0999ba154915eee201bd7a037e223e9368a97d

Tag:
https://gitbox.apache.org/repos/asf?p=calcite-avatica.git;a=tag;h=refs/tags/avatica-1.24.0-rc1

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-1.24.0-rc1
(revision 65633)

The hashes of the artifacts are as follows:
41da104d811b3925cbf19452cbe3acac8271bae188efb21f4eed9738dd13b1e353923f63a5ed73aefb05a1d5004211e0d438520b268c9e5d3f3f6c8f98c3be00
*apache-calcite-avatica-1.24.0-src.tar.gz

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1222/org/apache/calcite/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/francischuang.asc
https://www.apache.org/dist/calcite/KEYS

To create the jars and test Apache Calcite Avatica: "gradle build 
-Prelease -PskipSign".


If you do not have a Java/Gradle environment available, you can run the 
tests using docker. To do so, install docker and docker-compose, then 
run "docker-compose run test" from the root of the directory.


Please vote on releasing this package as Apache Calcite Avatica 1.24.0.

The vote is open for the next 72 hours and passes if a majority of at
least three +1 PMC votes are cast.

[ ] +1 Release this package as Apache Calcite Avatica 1.24.0
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...


Here is my vote:

+1 (binding)

Francis

[CANCEL][VOTE] Release Apache Calcite Avatica 1.24.0 (release candidate 0)

[Francis Chuang]

The vote has been cancelled to address issues building on JDK 8 due to 
incompatible dependencies.


On 28/11/2023 8:32 pm, Istvan Toth wrote:

Francis, The PQS build issue was caused by Avatica including some newer
dependencies (Jackson, IIRC), which include JVM dependent classes. The
current maven-shade-plugin version in PQS cannot handle those JARs, and
needs to be upgraded.
This is a PQS issue, and not  something that Avatica can or should fix.

The JVM 1.8 issue is specific to building Avatica, it doesn't affect
downstream projects that simply depend on the maven binaries.
I only encountered it, because I had to build the RC locally for testing,
and I do not trust the current cross-compile settings in the build.

I have tested Sergey's patch, and it solves the problem, it doesn't look
brittle to me, most related projects have similar workarounds for handling
JVM version differences.

Two different people have hit the JVM 1.8 building issue. Sergey's patch is
a simple fix, which prevents a lot of problems for people trying to build
Avatica in the future. My suggestion is to add it to 1.24.0 .

best regards
Istvan

On Mon, Nov 27, 2023 at 11:38 PM Francis Chuang 
wrote:


PQS already uses Avatica 1.23.0 [1], which already had the change to
upgrade checkstyle (which in turn required a newer version of Java).

I wonder if there's something else causing the issue Istvan is seeing.

[1] https://github.com/apache/phoenix-queryserver/blob/master/pom.xml#L88

On 28/11/2023 9:25 am, Julian Hyde wrote:

Istvan,

You must read the build instructions. If you do not read the build

instructions, you have no basis for voting -1.


Fixing gradle may or may not be the solution. (It might make gradle more

complex and fragile.)


Julian



On Nov 27, 2023, at 2:08 PM, Sergey Nuyanzin 

wrote:


Meanwhile I checked the code

the root cause of the behavior above is upgrade of checkstyle version

from

6.18 to 10.3.2 [1]
which happened in 1.23.0, i.e. it is reproducible with 1.23.0

in this case, please correct me if I'm wrong, this should not be

considered

as a blocker

[1] https://issues.apache.org/jira/browse/CALCITE-5329

On Mon, Nov 27, 2023 at 9:53 PM Sergey Nuyanzin 

wrote:



I created a PR[1]
The main idea is to introduce another property jdk8.checkstyle which is
set to 9.3
before resolving dependency for checkstyle it checks the current java
version. In case of 1.8 it uses new property otherwise the old one
new property also allows to keep ability to change version for jdk8

from

command line in case it is required as "-Pjdk8.checkstyle.version=X.Y"

Also it allows to compile with jdk 8, 11, 17 without explicitly set
checkstyle version

[1] https://github.com/apache/calcite-avatica/pull/233

On Mon, Nov 27, 2023 at 8:05 PM Istvan Toth 


wrote:


Can someone who knows Gradel make a patch to get Gradle to set
-Pcheckstyle.version=9.3 when it detects Java 1.8  ?
This is super simple in Maven with profiles, I expect that it should

not

be
very hard in Gradle either.

Also, I don't think that the exact JVM patch level has anything to do

with

this, as long as it's Java 1.8.

Istvan

On Mon, Nov 27, 2023 at 4:05 PM Guillaume Masse
 wrote:


Hi,

latest jdk 8 is 8u391, 8u371 is two version behind.





https://www.oracle.com/java/technologies/javase/8all-relnotes.html#R8u391-BPR





On Mon, Nov 27, 2023 at 4:21 AM Istvan Toth



wrote:


-1 (non binding)

I have successfully built and run the PQS test suite with the

Avatica

RC

with Java 11.
(I had to tweak the PQS maven setup a bit, but that's not Avatica's

fault)


When I tried to do the same with Java 8, I ran into the issues

mentioned

above.
I was able to hack around the checkstyle/autostyle issue by removing

them

from gradle build files, but then I got:

==
FAILURE: Build failed with an exception.

* Where:
Build file







'/home/stoty/workspaces/apache-phoenix/calcite-avatica/release/build.gradle.kts'

line: 213

* What went wrong:
Task with name 'assemble' not found in project ':release'.
==
and I wasn't able to get any further. (I am no Gradle expert)

Phoenix still supports Java 8, so we need the public artifacts to be

Java 8

compatible.
I imagine Phoenix is not the only project that still supports Java

8.


While Avatica is built with

sourceCompatibility = JavaVersion.VERSION_1_8

targetCompatibility = JavaVersion.VERSION_1_8
It does not seem to set the boot classpath, which does not guarantee

actual

backwards compatibility.
Depending on the Java APIs used, the generated code may or may not

work

on

Java 8 JVMs.

The easy workaround is to use the -release flag instead, but that

doesn't

work on Java 8, so this needs
some hacking of the build system.

best regards
Istvan


On Mon, Nov 27, 2023 at 7:13 AM Benchao Li 

wrote:



Thanks Francis for pointing it out, '-Pcheckstyle.version=9.3'

works

fine.


My vote is +1 (binding).

Francis

Re: [VOTE] Release Apache Calcite Avatica 1.24.0 (release candidate 0)

[Francis Chuang]

I am going to cancel this vote and make rc1 available for voting after 
the fix is merged.


On 28/11/2023 8:32 pm, Istvan Toth wrote:

Francis, The PQS build issue was caused by Avatica including some newer
dependencies (Jackson, IIRC), which include JVM dependent classes. The
current maven-shade-plugin version in PQS cannot handle those JARs, and
needs to be upgraded.
This is a PQS issue, and not  something that Avatica can or should fix.

The JVM 1.8 issue is specific to building Avatica, it doesn't affect
downstream projects that simply depend on the maven binaries.
I only encountered it, because I had to build the RC locally for testing,
and I do not trust the current cross-compile settings in the build.

I have tested Sergey's patch, and it solves the problem, it doesn't look
brittle to me, most related projects have similar workarounds for handling
JVM version differences.

Two different people have hit the JVM 1.8 building issue. Sergey's patch is
a simple fix, which prevents a lot of problems for people trying to build
Avatica in the future. My suggestion is to add it to 1.24.0 .

best regards
Istvan

On Mon, Nov 27, 2023 at 11:38 PM Francis Chuang 
wrote:


PQS already uses Avatica 1.23.0 [1], which already had the change to
upgrade checkstyle (which in turn required a newer version of Java).

I wonder if there's something else causing the issue Istvan is seeing.

[1] https://github.com/apache/phoenix-queryserver/blob/master/pom.xml#L88

On 28/11/2023 9:25 am, Julian Hyde wrote:

Istvan,

You must read the build instructions. If you do not read the build

instructions, you have no basis for voting -1.


Fixing gradle may or may not be the solution. (It might make gradle more

complex and fragile.)


Julian



On Nov 27, 2023, at 2:08 PM, Sergey Nuyanzin 

wrote:


Meanwhile I checked the code

the root cause of the behavior above is upgrade of checkstyle version

from

6.18 to 10.3.2 [1]
which happened in 1.23.0, i.e. it is reproducible with 1.23.0

in this case, please correct me if I'm wrong, this should not be

considered

as a blocker

[1] https://issues.apache.org/jira/browse/CALCITE-5329

On Mon, Nov 27, 2023 at 9:53 PM Sergey Nuyanzin 

wrote:



I created a PR[1]
The main idea is to introduce another property jdk8.checkstyle which is
set to 9.3
before resolving dependency for checkstyle it checks the current java
version. In case of 1.8 it uses new property otherwise the old one
new property also allows to keep ability to change version for jdk8

from

command line in case it is required as "-Pjdk8.checkstyle.version=X.Y"

Also it allows to compile with jdk 8, 11, 17 without explicitly set
checkstyle version

[1] https://github.com/apache/calcite-avatica/pull/233

On Mon, Nov 27, 2023 at 8:05 PM Istvan Toth 


wrote:


Can someone who knows Gradel make a patch to get Gradle to set
-Pcheckstyle.version=9.3 when it detects Java 1.8  ?
This is super simple in Maven with profiles, I expect that it should

not

be
very hard in Gradle either.

Also, I don't think that the exact JVM patch level has anything to do

with

this, as long as it's Java 1.8.

Istvan

On Mon, Nov 27, 2023 at 4:05 PM Guillaume Masse
 wrote:


Hi,

latest jdk 8 is 8u391, 8u371 is two version behind.





https://www.oracle.com/java/technologies/javase/8all-relnotes.html#R8u391-BPR





On Mon, Nov 27, 2023 at 4:21 AM Istvan Toth



wrote:


-1 (non binding)

I have successfully built and run the PQS test suite with the

Avatica

RC

with Java 11.
(I had to tweak the PQS maven setup a bit, but that's not Avatica's

fault)


When I tried to do the same with Java 8, I ran into the issues

mentioned

above.
I was able to hack around the checkstyle/autostyle issue by removing

them

from gradle build files, but then I got:

==
FAILURE: Build failed with an exception.

* Where:
Build file







'/home/stoty/workspaces/apache-phoenix/calcite-avatica/release/build.gradle.kts'

line: 213

* What went wrong:
Task with name 'assemble' not found in project ':release'.
==
and I wasn't able to get any further. (I am no Gradle expert)

Phoenix still supports Java 8, so we need the public artifacts to be

Java 8

compatible.
I imagine Phoenix is not the only project that still supports Java

8.


While Avatica is built with

sourceCompatibility = JavaVersion.VERSION_1_8

targetCompatibility = JavaVersion.VERSION_1_8
It does not seem to set the boot classpath, which does not guarantee

actual

backwards compatibility.
Depending on the Java APIs used, the generated code may or may not

work

on

Java 8 JVMs.

The easy workaround is to use the -release flag instead, but that

doesn't

work on Java 8, so this needs
some hacking of the build system.

best regards
Istvan


On Mon, Nov 27, 2023 at 7:13 AM Benchao Li 

wrote:



Thanks Francis for pointing it out, '-Pcheckstyle.version=9.3'

works

fine.


My vote is +1 (binding).

Francis Chuang 

Re: avatica-go: resultset offset management

[Francis Chuang]

Just wanted to quickly update with some investigation I have done with 
the test project [1]. I am testing against the Avatica HSQLDB server and 
it appears that the offset is never populated in the frames that are 
returned from the server, so that might be the cause.


[1] https://github.com/F21/avatica-go-test

On 28/11/2023 9:37 am, Julian Hyde wrote:

Egor,

I don’t know whether your hypothesis is correct, but it sounds plausible and 
well-researched. Therefore I think you should put it into a jira case, so the 
issue and discussion is on the record. If there is a flaw in your argument and 
the jira case is subsequently closed, there’s no shame in that.

Julian



On Nov 27, 2023, at 10:59 AM, Egor Ryashin  wrote:

Hi all,

this exception happens when Apache Druid Avatica protobuf endpoint is used: 
"Druid can only fetch forward. Requested offset”.
I tried to debug that and saw that any simple query fails if it triggers 
fetching of multiple frames. I speculate that when the first ExucuteRequest is 
sent

msg := {
StatementHandle:s.handle,
ParameterValues:s.parametersToTypedValues(args),
FirstFrameMaxSize:  s.conn.config.frameMaxSize,
HasParameterValues: true,
}

and the result set is created after

rsets = append(rsets, {
columns: columns,
done:frame.Done,
offset:  frame.Offset,
data:data,
})

then for the next frame FetchRequest is sent but it uses the same 0 offset (the 
data for that offset was returned with the ExecuteRequest)

res, err := r.conn.httpClient.post(context.Background(), 
{
ConnectionId: r.conn.connectionId,
StatementId:  r.statementID,
Offset:   resultSet.offset,
FrameMaxSize: r.conn.config.frameMaxSize,
})

So, in short, I think Avatica-Go sends 2 requests with the same offset that 
makes Druid to fail.

I wonder if anyone with more experience could confirm that?

The implementation I mentioned is here: 
go/pkg/mod/github.com/rilldata/calcite-avatica-go/v5@v5.0.0-20230621112535-eea498ff2a3d/rows.go

Thanks

Re: avatica-go: resultset offset management

[Francis Chuang]

Hi Egor,

As Julian mentioned, please open a jira issue and we can further debug 
and find the root cause.


Can you also switch to the apace/calcite-avatica-go repo (rather than 
rilldata's), so that we're looking at the same code?


Would you be also able to edit your local copy of calcite-avatica-go to 
add some print statements to print the offset? That way, we can see if 
the offset sent back from druid is correct.


I don't have druid set up so I currently don't have any way to reproduce 
this. I did however, create a test repo to force multiple fetches [2], 
to run it, run "docker compose run test" from the root of the project.


Francis

[1] https://github.com/apache/calcite-avatica-go/blame/main/rows.go#L86
[2] https://github.com/F21/avatica-go-test


On 28/11/2023 9:37 am, Julian Hyde wrote:

Egor,

I don’t know whether your hypothesis is correct, but it sounds plausible and 
well-researched. Therefore I think you should put it into a jira case, so the 
issue and discussion is on the record. If there is a flaw in your argument and 
the jira case is subsequently closed, there’s no shame in that.

Julian



On Nov 27, 2023, at 10:59 AM, Egor Ryashin  wrote:

Hi all,

this exception happens when Apache Druid Avatica protobuf endpoint is used: 
"Druid can only fetch forward. Requested offset”.
I tried to debug that and saw that any simple query fails if it triggers 
fetching of multiple frames. I speculate that when the first ExucuteRequest is 
sent

msg := {
StatementHandle:s.handle,
ParameterValues:s.parametersToTypedValues(args),
FirstFrameMaxSize:  s.conn.config.frameMaxSize,
HasParameterValues: true,
}

and the result set is created after

rsets = append(rsets, {
columns: columns,
done:frame.Done,
offset:  frame.Offset,
data:data,
})

then for the next frame FetchRequest is sent but it uses the same 0 offset (the 
data for that offset was returned with the ExecuteRequest)

res, err := r.conn.httpClient.post(context.Background(), 
{
ConnectionId: r.conn.connectionId,
StatementId:  r.statementID,
Offset:   resultSet.offset,
FrameMaxSize: r.conn.config.frameMaxSize,
})

So, in short, I think Avatica-Go sends 2 requests with the same offset that 
makes Druid to fail.

I wonder if anyone with more experience could confirm that?

The implementation I mentioned is here: 
go/pkg/mod/github.com/rilldata/calcite-avatica-go/v5@v5.0.0-20230621112535-eea498ff2a3d/rows.go

Thanks

Re: [VOTE] Release Apache Calcite Avatica 1.24.0 (release candidate 0)

[Francis Chuang]

PQS already uses Avatica 1.23.0 [1], which already had the change to 
upgrade checkstyle (which in turn required a newer version of Java).


I wonder if there's something else causing the issue Istvan is seeing.

[1] https://github.com/apache/phoenix-queryserver/blob/master/pom.xml#L88

On 28/11/2023 9:25 am, Julian Hyde wrote:

Istvan,

You must read the build instructions. If you do not read the build 
instructions, you have no basis for voting -1.

Fixing gradle may or may not be the solution. (It might make gradle more 
complex and fragile.)

Julian



On Nov 27, 2023, at 2:08 PM, Sergey Nuyanzin  wrote:

Meanwhile I checked the code

the root cause of the behavior above is upgrade of checkstyle version from
6.18 to 10.3.2 [1]
which happened in 1.23.0, i.e. it is reproducible with 1.23.0

in this case, please correct me if I'm wrong, this should not be considered
as a blocker

[1] https://issues.apache.org/jira/browse/CALCITE-5329

On Mon, Nov 27, 2023 at 9:53 PM Sergey Nuyanzin  wrote:


I created a PR[1]
The main idea is to introduce another property jdk8.checkstyle which is
set to 9.3
before resolving dependency for checkstyle it checks the current java
version. In case of 1.8 it uses new property otherwise the old one
new property also allows to keep ability to change version for jdk8 from
command line in case it is required as "-Pjdk8.checkstyle.version=X.Y"

Also it allows to compile with jdk 8, 11, 17 without explicitly set
checkstyle version

[1] https://github.com/apache/calcite-avatica/pull/233

On Mon, Nov 27, 2023 at 8:05 PM Istvan Toth 
wrote:


Can someone who knows Gradel make a patch to get Gradle to set
-Pcheckstyle.version=9.3 when it detects Java 1.8  ?
This is super simple in Maven with profiles, I expect that it should not
be
very hard in Gradle either.

Also, I don't think that the exact JVM patch level has anything to do with
this, as long as it's Java 1.8.

Istvan

On Mon, Nov 27, 2023 at 4:05 PM Guillaume Masse
 wrote:


Hi,

latest jdk 8 is 8u391, 8u371 is two version behind.



https://www.oracle.com/java/technologies/javase/8all-relnotes.html#R8u391-BPR





On Mon, Nov 27, 2023 at 4:21 AM Istvan Toth 
-1 (non binding)

I have successfully built and run the PQS test suite with the Avatica

RC

with Java 11.
(I had to tweak the PQS maven setup a bit, but that's not Avatica's

fault)


When I tried to do the same with Java 8, I ran into the issues

mentioned

above.
I was able to hack around the checkstyle/autostyle issue by removing

them

from gradle build files, but then I got:

==
FAILURE: Build failed with an exception.

* Where:
Build file





'/home/stoty/workspaces/apache-phoenix/calcite-avatica/release/build.gradle.kts'

line: 213

* What went wrong:
Task with name 'assemble' not found in project ':release'.
==
and I wasn't able to get any further. (I am no Gradle expert)

Phoenix still supports Java 8, so we need the public artifacts to be

Java 8

compatible.
I imagine Phoenix is not the only project that still supports Java 8.

While Avatica is built with

sourceCompatibility = JavaVersion.VERSION_1_8

targetCompatibility = JavaVersion.VERSION_1_8
It does not seem to set the boot classpath, which does not guarantee

actual

backwards compatibility.
Depending on the Java APIs used, the generated code may or may not

work

on

Java 8 JVMs.

The easy workaround is to use the -release flag instead, but that

doesn't

work on Java 8, so this needs
some hacking of the build system.

best regards
Istvan


On Mon, Nov 27, 2023 at 7:13 AM Benchao Li 

wrote:



Thanks Francis for pointing it out, '-Pcheckstyle.version=9.3' works

fine.


My vote is +1 (binding).

Francis Chuang  于2023年11月27日周一 13:12写道：


I think we need to force an older version of Checkstyle when using

JDK8.

See:








https://issues.apache.org/jira/browse/CALCITE-5329?focusedCommentId=17628456=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17628456


On 27/11/2023 3:55 pm, Benchao Li wrote:

- Verified checksum and signature (OK)
- Gone through release note (OK)
- Diffed source release with git repo (OK)
- Checked files in Nexus (OK)
- Compile and test sources with JDK8 (NOT SURE)

While compiling the sources with JDK8, I've encountered:
$java -version
java version "1.8.0_371"
Java(TM) SE Runtime Environment (build 1.8.0_371-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.371-b11, mixed mode)
$./gradlew build
FAILURE: Build completed with 5 failures.

1: Task failed with an exception.
---
* What went wrong:
Execution failed for task ':metrics:checkstyleMain'.

A failure occurred while executing

org.gradle.api.plugins.quality.internal.CheckstyleAction

com/puppycrawl/tools/checkstyle/ant/CheckstyleAntTask has

been

compiled by a more recent version of the Java Runtime (class

file

version 55.0), this version of the Java Runtime only recognizes

cla

Re: [VOTE] Release Apache Calcite Avatica 1.24.0 (release candidate 0)

[Francis Chuang]

I think we need to force an older version of Checkstyle when using JDK8. 
See: 
https://issues.apache.org/jira/browse/CALCITE-5329?focusedCommentId=17628456=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17628456


On 27/11/2023 3:55 pm, Benchao Li wrote:

- Verified checksum and signature (OK)
- Gone through release note (OK)
- Diffed source release with git repo (OK)
- Checked files in Nexus (OK)
- Compile and test sources with JDK8 (NOT SURE)

While compiling the sources with JDK8, I've encountered:
$java -version
java version "1.8.0_371"
Java(TM) SE Runtime Environment (build 1.8.0_371-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.371-b11, mixed mode)
$./gradlew build
FAILURE: Build completed with 5 failures.

1: Task failed with an exception.
---
* What went wrong:
Execution failed for task ':metrics:checkstyleMain'.

A failure occurred while executing 
org.gradle.api.plugins.quality.internal.CheckstyleAction

> com/puppycrawl/tools/checkstyle/ant/CheckstyleAntTask has been
compiled by a more recent version of the Java Runtime (class file
version 55.0), this version of the Java Runtime only recognizes class
file versions up to 52.0

Francis Chuang  于2023年11月27日周一 07:54写道：


Hi all,

I have created a build for Apache Calcite Avatica 1.24.0, release
candidate 0.

Thanks to everyone who has contributed to this release.

You can read the release notes here:
https://github.com/apache/calcite-avatica/blob/avatica-1.24.0-rc0/site/_docs/history.md

The commit to be voted upon:
https://gitbox.apache.org/repos/asf?p=calcite-avatica.git;a=commit;h=01a7a9e956b3fe8ad999a5b82e5d9924434cb309

Its hash is 01a7a9e956b3fe8ad999a5b82e5d9924434cb309

Tag:
https://github.com/apache/calcite-avatica/tree/avatica-1.24.0-rc0

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-1.24.0-rc0

The hashes of the artifacts are as follows:
927707b23a1338105fbb9d0a9a1836baf3e95e20002407b483b8f663927c5d41d844b2a09ec2cd1e580ae2e29d930ad32ee308d0d04550c35d8daefa7ad777c3
*apache-calcite-avatica-1.24.0-src.tar.gz

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1221/org/apache/calcite/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/francischuang.asc
https://www.apache.org/dist/calcite/KEYS

To create the jars and test Apache Calcite Avatica: "gradle build
-Prelease -PskipSign".

If you do not have a Java/Gradle environment available, you can run the
tests using docker. To do so, install docker and docker-compose, then
run "docker-compose run test" from the root of the directory.

Please vote on releasing this package as Apache Calcite Avatica 1.24.0.

The vote is open for the next 72 hours and passes if a majority of at
least three +1 PMC votes are cast.

[ ] +1 Release this package as Apache Calcite Avatica 1.24.0
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...


Here is my vote:

+1 (binding)

Francis

[VOTE] Release Apache Calcite Avatica 1.24.0 (release candidate 0)

[Francis Chuang]

Hi all,

I have created a build for Apache Calcite Avatica 1.24.0, release
candidate 0.

Thanks to everyone who has contributed to this release.

You can read the release notes here:
https://github.com/apache/calcite-avatica/blob/avatica-1.24.0-rc0/site/_docs/history.md

The commit to be voted upon:
https://gitbox.apache.org/repos/asf?p=calcite-avatica.git;a=commit;h=01a7a9e956b3fe8ad999a5b82e5d9924434cb309

Its hash is 01a7a9e956b3fe8ad999a5b82e5d9924434cb309

Tag:
https://github.com/apache/calcite-avatica/tree/avatica-1.24.0-rc0

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-1.24.0-rc0

The hashes of the artifacts are as follows:
927707b23a1338105fbb9d0a9a1836baf3e95e20002407b483b8f663927c5d41d844b2a09ec2cd1e580ae2e29d930ad32ee308d0d04550c35d8daefa7ad777c3
*apache-calcite-avatica-1.24.0-src.tar.gz

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachecalcite-1221/org/apache/calcite/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/francischuang.asc
https://www.apache.org/dist/calcite/KEYS

To create the jars and test Apache Calcite Avatica: "gradle build 
-Prelease -PskipSign".


If you do not have a Java/Gradle environment available, you can run the 
tests using docker. To do so, install docker and docker-compose, then 
run "docker-compose run test" from the root of the directory.


Please vote on releasing this package as Apache Calcite Avatica 1.24.0.

The vote is open for the next 72 hours and passes if a majority of at
least three +1 PMC votes are cast.

[ ] +1 Release this package as Apache Calcite Avatica 1.24.0
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...


Here is my vote:

+1 (binding)

Francis

Re: Towards Avatica 1.24.0 and Avatica-Go 5.3.0

[Francis Chuang]

Thank you for taking a look and merging the PRs, Istvan.

@All, I plan to make rc0 available for voting on 27 November 2023. If 
you'd like to get any commits in, or merge any PRs, please do so before 
then.


Francis

On 13/11/2023 5:25 pm, Istvan Toth wrote:

Hi!
I made a pass over the newer open pull requests, and committed
https://issues.apache.org/jira/browse/CALCITE-5536.

https://github.com/apache/calcite-avatica/pull/215 also looks
unctroversial, but it doesn't have a JIRA, and I'm not an Idea user, so I
cannot test it easily.

The rest do not seem to have consensus on them.
The timestamp patches have several unanswered suggestions and no approvals.
https://issues.apache.org/jira/browse/CALCITE-5957 seems to be a no go.
I have suggested a more generic approach for
https://issues.apache.org/jira/browse/CALCITE-5534 (though this on COULD be
committed)
The rest are older than the latest release, so I assume that they were not
included for a reason,

This does not mean that they can not be reviewed and merged, but most of
them are not super low hanging fruit.

Istvan


On Sun, Nov 12, 2023 at 10:35 PM Francis Chuang 
wrote:


Hey everyone,

Since Calcite 1.36.0 has been released, I think it would be a good time
to release Avatica 1.24.0 and Avatica-Go 5.3.0.

I will be release manager for both releases, with Avatica being released
first, followed by Avatica-Go.

For Avatica, can community members please review and merge the open pull
requests? There are quite a few that look like they are ready and a few
that can be merged with some work.

I am looking at making rc0 available for voting in around 2 weeks, to
allow for time to merge any open PRs, but I am happy to extend that if
needed.

Francis

[jira] [Created] (CALCITE-6110) Release Avatica-Go 5.3.0

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6110:
---

 Summary: Release Avatica-Go 5.3.0
 Key: CALCITE-6110
 URL: https://issues.apache.org/jira/browse/CALCITE-6110
 Project: Calcite
  Issue Type: New Feature
  Components: avatica-go
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: avatica-go-5.3.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Towards Avatica 1.24.0 and Avatica-Go 5.3.0

[Francis Chuang]

Hey everyone,

Since Calcite 1.36.0 has been released, I think it would be a good time 
to release Avatica 1.24.0 and Avatica-Go 5.3.0.


I will be release manager for both releases, with Avatica being released 
first, followed by Avatica-Go.


For Avatica, can community members please review and merge the open pull 
requests? There are quite a few that look like they are ready and a few 
that can be merged with some work.


I am looking at making rc0 available for voting in around 2 weeks, to 
allow for time to merge any open PRs, but I am happy to extend that if 
needed.


Francis

[jira] [Created] (CALCITE-6107) Upgrade vlsi-release-plugins to 1.90

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6107:
---

 Summary: Upgrade vlsi-release-plugins to 1.90
 Key: CALCITE-6107
 URL: https://issues.apache.org/jira/browse/CALCITE-6107
 Project: Calcite
  Issue Type: New Feature
  Components: avatica, core
Reporter: Francis Chuang
Assignee: Francis Chuang






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Fake release for Calcite pushed and deleted

[Francis Chuang]

This is just a quick heads up for people watching the tags for the 
Calcite repository.


To fix the javadocs not being built when 1.36.0 was released, I had to 
commit CALCITE-6103 [1]. In order to force the javadocs to build on 
GitHub actions, I had to create a fake release for calcite-1.36.1 to 
trigger the job. The release/tag has since been deleted once the 
workflow was started.


Francis

[1] https://issues.apache.org/jira/browse/CALCITE-6103

Re: [DISCUSS] Towards Calcite 1.36.0

[Francis Chuang]

I committed CALCITE-6103 in https://github.com/apache/calcite/pull/3516 
and built the javadocs in 
https://github.com/apache/calcite/actions/runs/6833129020/job/18584563071


On 10/11/2023 10:06 pm, Benchao Li wrote:

Thanks Francis, I'll proceed with next steps now.

Francis Chuang  于2023年11月10日周五 19:01写道：


I think something has changed in the openjdk image used to build the
javadocs.

See:
https://stackoverflow.com/questions/73516116/got-error-xargs-is-not-available-when-trying-to-run-a-docker-image/75660631#75660631

I think we need to move to the eclipse-temurin images as the openjdk
images have been EOL for a while.

I think just leave the javadoc publishing for now, as I'll open a PR
after the release to fix this.

Francis

On 10/11/2023 9:50 pm, Benchao Li wrote:

Thanks Francis for your response.

There is one more problem, that the CI for releasing javadoc[1] is
failing with "xargs is not available".

[1] https://github.com/apache/calcite/actions/runs/6822762022/job/18555648165

Francis Chuang  于2023年11月10日周五 18:18写道：


I do see 1.36.0 on ASF Nexus (https://repository.apache.org/) I wonder
if it's just replication lag.

On 10/11/2023 9:07 pm, Benchao Li wrote:

Hi all,

I met some problems while publishing.

The command I'm using is `./gradlew publishDist -Prc=0 -Pasf
-Pasf.git.pushRepositoryProvider=GITHUB`. Although the command ran
successfully, I noticed the 'releaseRepository' prints somethings
wield, and actually there is no 1.36.0 in nexus yet[1]. , Below is all
the output from it:

Starting a Gradle Daemon (subsequent builds will be faster)


Configure project :

Building Apache Calcite 1.36.0


Task :publishSvnDist

Listing SVN folders [dev/calcite/apache-calcite-1.36.0-rc0] at
https://dist.apache.org/repos/dist
Executing svnmucc. root=https://dist.apache.org/repos/dist,
message=Promoting Apache Calcite calcite-1.36.0-rc0 -> calcite-1.36.0
to release area, commands:
mkdir
release/calcite/apache-calcite-1.36.0
cp
65079
dev/calcite/apache-calcite-1.36.0-rc0/apache-calcite-1.36.0-src.tar.gz
release/calcite/apache-calcite-1.36.0/apache-calcite-1.36.0-src.tar.gz
cp
65079
dev/calcite/apache-calcite-1.36.0-rc0/apache-calcite-1.36.0-src.tar.gz.asc
release/calcite/apache-calcite-1.36.0/apache-calcite-1.36.0-src.tar.gz.asc
cp
65079
dev/calcite/apache-calcite-1.36.0-rc0/apache-calcite-1.36.0-src.tar.gz.sha512
release/calcite/apache-calcite-1.36.0/apache-calcite-1.36.0-src.tar.gz.sha512
rm
dev/calcite/apache-calcite-1.36.0-rc0
r65191 committed by libenchao at 2023-11-10T08:56:00.445211Z


Task :releaseRepository

Initialized stagingRepositoryId orgapachecalcite-1219 for repository nexus
GET request failed. 404: Not Found, body: [errors:[[id:*, msg:No such
repository: orgapachecalcite-1219]]]
Requested operation was executed successfully in attempt 83 (maximum
allowed 601)


Task :createReleaseTag

Created tag calcite-1.36.0 ->
Ref[refs/tags/calcite-1.36.0=450f51a96db8253e0ae62661e3be46a707a2cd8c(-1)]


Task :pushReleaseTag

Pushing tag to Git remote release-origin: https://github.com/apache/calcite.git
Message from release-origin:
 refs/tags/calcite-1.36.0: OK,
450f51a96db8253e0ae62661e3be46a707a2cd8c (fastForward)

Deprecated Gradle features were used in this build, making it
incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation
warnings and determine if they come from your own scripts or plugins.

See 
https://docs.gradle.org/7.6.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 5m 4s
34 actionable tasks: 4 executed, 30 up-to-date


[1] https://mvnrepository.com/artifact/org.apache.calcite/calcite-core

Tanner Clary  于2023年11月8日周三 11:18写道：


Sounds good, I'll keep track of that and make sure it gets rebased.

On Tue, Nov 7, 2023 at 7:01 PM Francis Chuang 
wrote:


Looks great, Tanner!

As the original PR has been merged and cannot be reopened, let's
remember to rebase the commit onto main after 1.36.0 has been released.

On 8/11/2023 1:58 pm, Tanner Clary wrote:

Ok I believe I reset main to


https://github.com/apache/calcite/commit/4c9011c388f826c36463ae7da875ddb525104376

.
Feel free to take a look at

https://github.com/apache/calcite/commits/main

and let me know if I've made any mistakes. Sorry for any confusion and
thanks for your patience.

Best,
Tanner

On Tue, Nov 7, 2023 at 6:54 PM Tanner Clary 

wrote:



Oops I took revert too literally. I can reset it two commits (the revert
commit and the commit I reverted). Sorry for the misunderstanding.

Tanner

On Tue, Nov 7, 2023 at 6:49 PM Benchao Li  wrote:


Tanner,

By saying "revert", I think we actually mean "reset to earlier
commit(


https://github.com/apache/calcite/commit/4c9011c388f826c36463ae7da875ddb525104376

),
and force push main branch". Because the commit we are voting on is



https://github.com/apache/calcite/commit/0be8eaebcf27afae9ecda8ab79db63c214426561

,
after the voting, I'll push it to main with a

[jira] [Created] (CALCITE-6106) Switch from gradle to eclipse-temurin image for avatica docker-compose release commands

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6106:
---

 Summary: Switch from gradle to eclipse-temurin image for avatica 
docker-compose release commands
 Key: CALCITE-6106
 URL: https://issues.apache.org/jira/browse/CALCITE-6106
 Project: Calcite
  Issue Type: New Feature
  Components: avatica
Reporter: Francis Chuang
Assignee: Francis Chuang


Switch to the eclipse-temurin image and call ./gradlew instead of gradle, so 
the gradle version used is never out of sync.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (CALCITE-6103) Use eclipse-temurin to build and publish javadocs for the website

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6103:
---

 Summary: Use eclipse-temurin to build and publish javadocs for the 
website
 Key: CALCITE-6103
 URL: https://issues.apache.org/jira/browse/CALCITE-6103
 Project: Calcite
  Issue Type: New Feature
  Components: avatica, core, site
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: 1.37.0


Javadoc builds currently fail in GitHub Actions:

{code:java}
Run docker-compose run generate-javadoc
  
Pulling generate-javadoc (openjdk:17)...
17: Pulling from library/openjdk
Digest: sha256:528707081fdb9562eb819128a9f85ae7fe000e2fbaeaf9f87662e7b3f38cb7d8
Status: Downloaded newer image for openjdk:17
Creating site_generate-javadoc_run ... 
Creating site_generate-javadoc_run ... done

xargs is not available

mv: cannot stat 'build/docs/javadocAggregate': No such file or directory
1
Error: Process completed with exit code 1.
{code}

There was probably a change in the openjdk:17 image, which has since been 
deprecated. As a fix, we should move to the eclipse-temurin, which is a direct 
replacement.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Towards Calcite 1.36.0

[Francis Chuang]

I think something has changed in the openjdk image used to build the 
javadocs.


See: 
https://stackoverflow.com/questions/73516116/got-error-xargs-is-not-available-when-trying-to-run-a-docker-image/75660631#75660631


I think we need to move to the eclipse-temurin images as the openjdk 
images have been EOL for a while.


I think just leave the javadoc publishing for now, as I'll open a PR 
after the release to fix this.


Francis

On 10/11/2023 9:50 pm, Benchao Li wrote:

Thanks Francis for your response.

There is one more problem, that the CI for releasing javadoc[1] is
failing with "xargs is not available".

[1] https://github.com/apache/calcite/actions/runs/6822762022/job/18555648165

Francis Chuang  于2023年11月10日周五 18:18写道：


I do see 1.36.0 on ASF Nexus (https://repository.apache.org/) I wonder
if it's just replication lag.

On 10/11/2023 9:07 pm, Benchao Li wrote:

Hi all,

I met some problems while publishing.

The command I'm using is `./gradlew publishDist -Prc=0 -Pasf
-Pasf.git.pushRepositoryProvider=GITHUB`. Although the command ran
successfully, I noticed the 'releaseRepository' prints somethings
wield, and actually there is no 1.36.0 in nexus yet[1]. , Below is all
the output from it:

Starting a Gradle Daemon (subsequent builds will be faster)


Configure project :

Building Apache Calcite 1.36.0


Task :publishSvnDist

Listing SVN folders [dev/calcite/apache-calcite-1.36.0-rc0] at
https://dist.apache.org/repos/dist
Executing svnmucc. root=https://dist.apache.org/repos/dist,
message=Promoting Apache Calcite calcite-1.36.0-rc0 -> calcite-1.36.0
to release area, commands:
mkdir
release/calcite/apache-calcite-1.36.0
cp
65079
dev/calcite/apache-calcite-1.36.0-rc0/apache-calcite-1.36.0-src.tar.gz
release/calcite/apache-calcite-1.36.0/apache-calcite-1.36.0-src.tar.gz
cp
65079
dev/calcite/apache-calcite-1.36.0-rc0/apache-calcite-1.36.0-src.tar.gz.asc
release/calcite/apache-calcite-1.36.0/apache-calcite-1.36.0-src.tar.gz.asc
cp
65079
dev/calcite/apache-calcite-1.36.0-rc0/apache-calcite-1.36.0-src.tar.gz.sha512
release/calcite/apache-calcite-1.36.0/apache-calcite-1.36.0-src.tar.gz.sha512
rm
dev/calcite/apache-calcite-1.36.0-rc0
r65191 committed by libenchao at 2023-11-10T08:56:00.445211Z


Task :releaseRepository

Initialized stagingRepositoryId orgapachecalcite-1219 for repository nexus
GET request failed. 404: Not Found, body: [errors:[[id:*, msg:No such
repository: orgapachecalcite-1219]]]
Requested operation was executed successfully in attempt 83 (maximum
allowed 601)


Task :createReleaseTag

Created tag calcite-1.36.0 ->
Ref[refs/tags/calcite-1.36.0=450f51a96db8253e0ae62661e3be46a707a2cd8c(-1)]


Task :pushReleaseTag

Pushing tag to Git remote release-origin: https://github.com/apache/calcite.git
Message from release-origin:
refs/tags/calcite-1.36.0: OK,
450f51a96db8253e0ae62661e3be46a707a2cd8c (fastForward)

Deprecated Gradle features were used in this build, making it
incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation
warnings and determine if they come from your own scripts or plugins.

See 
https://docs.gradle.org/7.6.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 5m 4s
34 actionable tasks: 4 executed, 30 up-to-date


[1] https://mvnrepository.com/artifact/org.apache.calcite/calcite-core

Tanner Clary  于2023年11月8日周三 11:18写道：


Sounds good, I'll keep track of that and make sure it gets rebased.

On Tue, Nov 7, 2023 at 7:01 PM Francis Chuang 
wrote:


Looks great, Tanner!

As the original PR has been merged and cannot be reopened, let's
remember to rebase the commit onto main after 1.36.0 has been released.

On 8/11/2023 1:58 pm, Tanner Clary wrote:

Ok I believe I reset main to


https://github.com/apache/calcite/commit/4c9011c388f826c36463ae7da875ddb525104376

.
Feel free to take a look at

https://github.com/apache/calcite/commits/main

and let me know if I've made any mistakes. Sorry for any confusion and
thanks for your patience.

Best,
Tanner

On Tue, Nov 7, 2023 at 6:54 PM Tanner Clary 

wrote:



Oops I took revert too literally. I can reset it two commits (the revert
commit and the commit I reverted). Sorry for the misunderstanding.

Tanner

On Tue, Nov 7, 2023 at 6:49 PM Benchao Li  wrote:


Tanner,

By saying "revert", I think we actually mean "reset to earlier
commit(


https://github.com/apache/calcite/commit/4c9011c388f826c36463ae7da875ddb525104376

),
and force push main branch". Because the commit we are voting on is



https://github.com/apache/calcite/commit/0be8eaebcf27afae9ecda8ab79db63c214426561

,
after the voting, I'll push it to main with additional commits
preparing for next version, then all the commits after



https://github.com/apache/calcite/commit/4c9011c388f826c36463ae7da875ddb525104376

will be invalid.

Tanner Clary  于2023年11月8日周三 10:43写道：


The commit reverting 3154708 is here:




https://github.com/apache/calcite/commit/213c

Re: [DISCUSS] Towards Calcite 1.36.0

[Francis Chuang]

I do see 1.36.0 on ASF Nexus (https://repository.apache.org/) I wonder 
if it's just replication lag.


On 10/11/2023 9:07 pm, Benchao Li wrote:

Hi all,

I met some problems while publishing.

The command I'm using is `./gradlew publishDist -Prc=0 -Pasf
-Pasf.git.pushRepositoryProvider=GITHUB`. Although the command ran
successfully, I noticed the 'releaseRepository' prints somethings
wield, and actually there is no 1.36.0 in nexus yet[1]. , Below is all
the output from it:

Starting a Gradle Daemon (subsequent builds will be faster)


Configure project :

Building Apache Calcite 1.36.0


Task :publishSvnDist

Listing SVN folders [dev/calcite/apache-calcite-1.36.0-rc0] at
https://dist.apache.org/repos/dist
Executing svnmucc. root=https://dist.apache.org/repos/dist,
message=Promoting Apache Calcite calcite-1.36.0-rc0 -> calcite-1.36.0
to release area, commands:
mkdir
release/calcite/apache-calcite-1.36.0
cp
65079
dev/calcite/apache-calcite-1.36.0-rc0/apache-calcite-1.36.0-src.tar.gz
release/calcite/apache-calcite-1.36.0/apache-calcite-1.36.0-src.tar.gz
cp
65079
dev/calcite/apache-calcite-1.36.0-rc0/apache-calcite-1.36.0-src.tar.gz.asc
release/calcite/apache-calcite-1.36.0/apache-calcite-1.36.0-src.tar.gz.asc
cp
65079
dev/calcite/apache-calcite-1.36.0-rc0/apache-calcite-1.36.0-src.tar.gz.sha512
release/calcite/apache-calcite-1.36.0/apache-calcite-1.36.0-src.tar.gz.sha512
rm
dev/calcite/apache-calcite-1.36.0-rc0
r65191 committed by libenchao at 2023-11-10T08:56:00.445211Z


Task :releaseRepository

Initialized stagingRepositoryId orgapachecalcite-1219 for repository nexus
GET request failed. 404: Not Found, body: [errors:[[id:*, msg:No such
repository: orgapachecalcite-1219]]]
Requested operation was executed successfully in attempt 83 (maximum
allowed 601)


Task :createReleaseTag

Created tag calcite-1.36.0 ->
Ref[refs/tags/calcite-1.36.0=450f51a96db8253e0ae62661e3be46a707a2cd8c(-1)]


Task :pushReleaseTag

Pushing tag to Git remote release-origin: https://github.com/apache/calcite.git
Message from release-origin:
   refs/tags/calcite-1.36.0: OK,
450f51a96db8253e0ae62661e3be46a707a2cd8c (fastForward)

Deprecated Gradle features were used in this build, making it
incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation
warnings and determine if they come from your own scripts or plugins.

See 
https://docs.gradle.org/7.6.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 5m 4s
34 actionable tasks: 4 executed, 30 up-to-date


[1] https://mvnrepository.com/artifact/org.apache.calcite/calcite-core

Tanner Clary  于2023年11月8日周三 11:18写道：


Sounds good, I'll keep track of that and make sure it gets rebased.

On Tue, Nov 7, 2023 at 7:01 PM Francis Chuang 
wrote:


Looks great, Tanner!

As the original PR has been merged and cannot be reopened, let's
remember to rebase the commit onto main after 1.36.0 has been released.

On 8/11/2023 1:58 pm, Tanner Clary wrote:

Ok I believe I reset main to


https://github.com/apache/calcite/commit/4c9011c388f826c36463ae7da875ddb525104376

.
Feel free to take a look at

https://github.com/apache/calcite/commits/main

and let me know if I've made any mistakes. Sorry for any confusion and
thanks for your patience.

Best,
Tanner

On Tue, Nov 7, 2023 at 6:54 PM Tanner Clary 

wrote:



Oops I took revert too literally. I can reset it two commits (the revert
commit and the commit I reverted). Sorry for the misunderstanding.

Tanner

On Tue, Nov 7, 2023 at 6:49 PM Benchao Li  wrote:


Tanner,

By saying "revert", I think we actually mean "reset to earlier
commit(


https://github.com/apache/calcite/commit/4c9011c388f826c36463ae7da875ddb525104376

),
and force push main branch". Because the commit we are voting on is



https://github.com/apache/calcite/commit/0be8eaebcf27afae9ecda8ab79db63c214426561

,
after the voting, I'll push it to main with additional commits
preparing for next version, then all the commits after



https://github.com/apache/calcite/commit/4c9011c388f826c36463ae7da875ddb525104376

will be invalid.

Tanner Clary  于2023年11月8日周三 10:43写道：


The commit reverting 3154708 is here:




https://github.com/apache/calcite/commit/213c13776651f83f95dceb9645a15e940ec6dce1


Let me know if I can do anything else to help and thank y'all for

handling

the release!

Best,
Tanner

On Tue, Nov 7, 2023 at 6:34 PM Tanner Clary 

wrote:



I can revert it if that's alright, hope this helps!

Best,
Tanner

On Tue, Nov 7, 2023 at 6:01 PM Francis Chuang <

francischu...@apache.org>

wrote:


I believe the main branch should still be frozen as we're still

voting

for 1.36.0.

I think 14ed78f22eb854fe4643c6e1faad5b0824733515 needs to be

reverted

and then rebased on to main after 1.36.0 has been released.

Francis

On 8/11/2023 12:58 pm, Jiajun Xie wrote:

Hi, Benchao

Is the main branch still frozen?

I found a new commit[1], but 1.36.0 has not been released.

[1]






https://

Re: [DISCUSS] Towards Calcite 1.36.0

[Francis Chuang]

Looks great, Tanner!

As the original PR has been merged and cannot be reopened, let's 
remember to rebase the commit onto main after 1.36.0 has been released.


On 8/11/2023 1:58 pm, Tanner Clary wrote:

Ok I believe I reset main to
https://github.com/apache/calcite/commit/4c9011c388f826c36463ae7da875ddb525104376
.
Feel free to take a look at https://github.com/apache/calcite/commits/main
and let me know if I've made any mistakes. Sorry for any confusion and
thanks for your patience.

Best,
Tanner

On Tue, Nov 7, 2023 at 6:54 PM Tanner Clary  wrote:


Oops I took revert too literally. I can reset it two commits (the revert
commit and the commit I reverted). Sorry for the misunderstanding.

Tanner

On Tue, Nov 7, 2023 at 6:49 PM Benchao Li  wrote:


Tanner,

By saying "revert", I think we actually mean "reset to earlier
commit(
https://github.com/apache/calcite/commit/4c9011c388f826c36463ae7da875ddb525104376
),
and force push main branch". Because the commit we are voting on is

https://github.com/apache/calcite/commit/0be8eaebcf27afae9ecda8ab79db63c214426561
,
after the voting, I'll push it to main with additional commits
preparing for next version, then all the commits after

https://github.com/apache/calcite/commit/4c9011c388f826c36463ae7da875ddb525104376
will be invalid.

Tanner Clary  于2023年11月8日周三 10:43写道：


The commit reverting 3154708 is here:


https://github.com/apache/calcite/commit/213c13776651f83f95dceb9645a15e940ec6dce1


Let me know if I can do anything else to help and thank y'all for

handling

the release!

Best,
Tanner

On Tue, Nov 7, 2023 at 6:34 PM Tanner Clary 

wrote:



I can revert it if that's alright, hope this helps!

Best,
Tanner

On Tue, Nov 7, 2023 at 6:01 PM Francis Chuang <

francischu...@apache.org>

wrote:


I believe the main branch should still be frozen as we're still

voting

for 1.36.0.

I think 14ed78f22eb854fe4643c6e1faad5b0824733515 needs to be reverted
and then rebased on to main after 1.36.0 has been released.

Francis

On 8/11/2023 12:58 pm, Jiajun Xie wrote:

Hi, Benchao

Is the main branch still frozen?

I found a new commit[1], but 1.36.0 has not been released.

[1]




https://github.com/apache/calcite/commit/3157408a127de0d5c1d6b440bd2086f96f4f91ba


On Mon, 6 Nov 2023 at 14:59, Benchao Li 

wrote:



The release note PR is now available for review:
https://github.com/apache/calcite/pull/3505

Benchao Li  于2023年11月6日周一 12:46写道：


Hi devs,

All the issues targeted for 1.36.0 have been resolved, I'll

start the

release process now. Therefore main branch is in code freeze

until

further notice.

Benchao Li  于2023年11月3日周五 10:50写道：


@Mihai @Julian The only left issue is 5884 now, can we merge it

and

start the releasing process?

LakeShen  于2023年11月1日周三 12:13写道：


Hi Itiel,

I have reviewd the

https://github.com/apache/calcite/pull/3325,and

left one

comments

Benchao Li  于2023年11月1日周三 10:17写道：


Mihai,
I've reviewed 5884, it looks good and I think we can have it

in

1.36.0


Itiel,
https://github.com/apache/calcite/pull/3325 has been

reviewed and

even

with an approval, I'll try to ping in the PR to try to get it

merged

in 1.36.0

Mihai Budiu  于2023年11月1日周三 02:42写道：


5884 is mostly documentation fixes.
I expected it would be easy to get it in.
But we can leave it for later.

Mihai


From: Benchao Li 
Sent: Tuesday, October 31, 2023 6:50 AM
To: dev@calcite.apache.org 
Subject: Re: [DISCUSS] Towards Calcite 1.36.0

Due to the inactivity of the review for CALCITE-5884 and

CALCITE-4455,

I think we can move it out of 1.36.0 for now. What do you

think?


Other three issues look promising to be merged soon, then

I'll

start

the release process after they are merged.

Julian Hyde  于2023年10月31日周二 02:31写道：


I just merged CALCITE-{129,6052}. Five left.


On Oct 30, 2023, at 7:22 AM, Ran Tao <

chucheng...@gmail.com>

wrote:


The expected release time at the end of the month seems to

be coming

soon.

I performed an update on the list compiled by Jiajun.

#1.Last update (new comments or commits) within 2 days

(almost

ready):

https://issues.apache.org/jira/browse/CALCITE-129
https://issues.apache.org/jira/browse/CALCITE-5826

#2. Last update exceeded 2 days
https://issues.apache.org/jira/browse/CALCITE-5990
https://issues.apache.org/jira/browse/CALCITE-5984
https://issues.apache.org/jira/browse/CALCITE-6052

#3. Last update exceeded 7 days
https://issues.apache.org/jira/browse/CALCITE-5884
https://issues.apache.org/jira/browse/CALCITE-4455

Best Regards,
Ran Tao


Jiajun Xie  于2023年10月28日周六

13:34写道：



Hi, all:
We're already very close to 1.36.0, all unresolved issues

has been

someone

reviewed.












https://issues.apache.org/jira/browse/CALCITE-6047?jql=project%20%3D%20CALCITE%20AND%20status%20%3D%20Open%20AND%20fixVersion%20%3D%201.36.0



- Some issues are currently being reviewed.
That's great! Thank you all for your efforts.
- Some issues have not been updated for a

Re: [DISCUSS] Towards Calcite 1.36.0

[Francis Chuang]

I believe the main branch should still be frozen as we're still voting 
for 1.36.0.


I think 14ed78f22eb854fe4643c6e1faad5b0824733515 needs to be reverted 
and then rebased on to main after 1.36.0 has been released.


Francis

On 8/11/2023 12:58 pm, Jiajun Xie wrote:

Hi, Benchao

Is the main branch still frozen?

I found a new commit[1], but 1.36.0 has not been released.

[1]
https://github.com/apache/calcite/commit/3157408a127de0d5c1d6b440bd2086f96f4f91ba

On Mon, 6 Nov 2023 at 14:59, Benchao Li  wrote:


The release note PR is now available for review:
https://github.com/apache/calcite/pull/3505

Benchao Li  于2023年11月6日周一 12:46写道：


Hi devs,

All the issues targeted for 1.36.0 have been resolved, I'll start the
release process now. Therefore main branch is in code freeze until
further notice.

Benchao Li  于2023年11月3日周五 10:50写道：


@Mihai @Julian The only left issue is 5884 now, can we merge it and
start the releasing process?

LakeShen  于2023年11月1日周三 12:13写道：


Hi Itiel,

I have reviewd the https://github.com/apache/calcite/pull/3325,and

left one

comments

Benchao Li  于2023年11月1日周三 10:17写道：


Mihai,
I've reviewed 5884, it looks good and I think we can have it in

1.36.0


Itiel,
https://github.com/apache/calcite/pull/3325 has been reviewed and

even

with an approval, I'll try to ping in the PR to try to get it

merged

in 1.36.0

Mihai Budiu  于2023年11月1日周三 02:42写道：


5884 is mostly documentation fixes.
I expected it would be easy to get it in.
But we can leave it for later.

Mihai


From: Benchao Li 
Sent: Tuesday, October 31, 2023 6:50 AM
To: dev@calcite.apache.org 
Subject: Re: [DISCUSS] Towards Calcite 1.36.0

Due to the inactivity of the review for CALCITE-5884 and

CALCITE-4455,

I think we can move it out of 1.36.0 for now. What do you think?

Other three issues look promising to be merged soon, then I'll

start

the release process after they are merged.

Julian Hyde  于2023年10月31日周二 02:31写道：


I just merged CALCITE-{129,6052}. Five left.


On Oct 30, 2023, at 7:22 AM, Ran Tao 

wrote:


The expected release time at the end of the month seems to

be coming

soon.

I performed an update on the list compiled by Jiajun.

#1.Last update (new comments or commits) within 2 days

(almost

ready):

https://issues.apache.org/jira/browse/CALCITE-129
https://issues.apache.org/jira/browse/CALCITE-5826

#2. Last update exceeded 2 days
https://issues.apache.org/jira/browse/CALCITE-5990
https://issues.apache.org/jira/browse/CALCITE-5984
https://issues.apache.org/jira/browse/CALCITE-6052

#3. Last update exceeded 7 days
https://issues.apache.org/jira/browse/CALCITE-5884
https://issues.apache.org/jira/browse/CALCITE-4455

Best Regards,
Ran Tao


Jiajun Xie  于2023年10月28日周六

13:34写道：



Hi, all:
We're already very close to 1.36.0, all unresolved issues

has been

someone

reviewed.








https://issues.apache.org/jira/browse/CALCITE-6047?jql=project%20%3D%20CALCITE%20AND%20status%20%3D%20Open%20AND%20fixVersion%20%3D%201.36.0



- Some issues are currently being reviewed.
That's great! Thank you all for your efforts.
- Some issues have not been updated for a long time.
If anyone is willing to continue the review, I believe they

should

be

resolved soon.


#1.Last update (new comments or commits) within 2 days:
https://issues.apache.org/jira/browse/CALCITE-129
https://issues.apache.org/jira/browse/CALCITE-5990

#2. Last update exceeded 2 days
https://issues.apache.org/jira/browse/CALCITE-5984
https://issues.apache.org/jira/browse/CALCITE-6052

#3. Last update exceeded 7 days
https://issues.apache.org/jira/browse/CALCITE-5884
https://issues.apache.org/jira/browse/CALCITE-6037

#4. Last update exceeded 14 days
https://issues.apache.org/jira/browse/CALCITE-4455
https://issues.apache.org/jira/browse/CALCITE-5826

On Wed, 25 Oct 2023 at 11:40, Benchao Li <

libenc...@apache.org>

wrote:



Thanks Mihai for the quick response, I'll take a look at

the PR.


Mihai Budiu  于2023年10月25日周三 05:02写道：


For the blocker issues, I have filed two PRs which should

collectively

fix them.


https://github.com/apache/calcite/pull/3481 fixes

https://issues.apache.org/jira/browse/CALCITE-5990, but

does not

include

tests, because the test fixture needs to be fixed as well

for the

tests

to

pass. There are tests in the next PR:

https://github.com/apache/calcite/pull/3471 fixes

https://issues.apache.org/jira/browse/CALCITE-5921, but

should be

amended

to reenable the disabled tests if we merge 3481 first.


Mihai


From: Benchao Li 
Sent: Tuesday, October 24, 2023 5:46 AM
To: dev@calcite.apache.org 
Subject: Re: [DISCUSS] Towards Calcite 1.36.0

A quick update on the current status for issues targeted

1.36.0


We need more reviewers for #2 and #3 since the end of

October is

approaching.

Please correct me if I'm mistaken, especially for issues

in #1.


#1. Issues already have reviewers, and seems promising to

be

merged

shortly

Re: [VOTE] Release Apache Calcite 1.36.0 (release candidate 0)

[Francis Chuang]

Thanks for being RM for this release, Benchao!

My vote is: +1 (binding)

- Verified GPG signature - OK
- Verified SHA512 - OK
- Diffed source release and git repository - OK
- Checked release notes on tag 
(https://github.com/apache/calcite/blob/calcite-1.36.0-rc0/site/_docs/history.md) 
- OK

- Checked year and versions in NOTICE, README and HOWTO - OK
- Ran tests (gradle check) - OK
- Spot checked Nexus artifacts - OK

Environment:
Eclipse-temurin:19-jammy docker container in WSL2 (Ubuntu 22.04.3) on 
Windows 11 22h2


$ docker version
Client: Docker Engine - Community
 Cloud integration: v1.0.35+desktop.5
 Version:   24.0.6
 API version:   1.43
 Go version:go1.20.7
 Git commit:ed223bc
 Built: Mon Sep  4 12:32:16 2023
 OS/Arch:   linux/amd64
 Context:   default

Server: Docker Desktop
 Engine:
  Version:  24.0.6
  API version:  1.43 (minimum version 1.12)
  Go version:   go1.20.7
  Git commit:   1a79695
  Built:Mon Sep  4 12:32:16 2023
  OS/Arch:  linux/amd64
  Experimental: false
 containerd:
  Version:  1.6.22
  GitCommit:8165feabfdfe38c65b599c4993d227328c231fca
 runc:
  Version:  1.1.8
  GitCommit:v1.1.8-0-g82f18fe
 docker-init:
  Version:  0.19.0
  GitCommit:de40ad0

$ gradle -v


Gradle 7.6.1


Build time:   2023-02-24 13:54:42 UTC
Revision: 3905fe8ac072bbd925c70ddbf4463341f4b4

Kotlin:   1.7.10
Groovy:   3.0.13
Ant:  Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM:  19.0.2 (Eclipse Adoptium 19.0.2+7)
OS:   Linux 5.15.90.1-microsoft-standard-WSL2 amd64

$ java --version
openjdk 19.0.2 2023-01-17
OpenJDK Runtime Environment Temurin-19.0.2+7 (build 19.0.2+7)
OpenJDK 64-Bit Server VM Temurin-19.0.2+7 (build 19.0.2+7, mixed mode, 
sharing)


Francis

On 8/11/2023 7:55 am, Julian Hyde wrote:

Oops, Ubuntu 23.10. Obviously.

On Tue, Nov 7, 2023 at 12:02 PM Julian Hyde  wrote:


+1 (binding)

Downloaded; checked signatures & hashes; checked LICENSE, NOTICE,
README, README.md, howto.md, history.md; ran RAT; compared to git tag.
Built and ran tests using Gradle 7.4.2, OpenJDK 19.0.2, Ubuntu 24.10.

Thanks Benchao!

Julian

On Tue, Nov 7, 2023 at 7:41 AM LakeShen  wrote:


Thanks to Benchao’s contributions

+1(binding)

Best,
LakeShen

Benchao Li  于2023年11月7日周二 13:20写道：


Hi all,

I have created a build for Apache Calcite 1.36.0, release
candidate 0.

Thanks to everyone who has contributed to this release.

You can read the release notes here:

https://github.com/apache/calcite/blob/calcite-1.36.0-rc0/site/_docs/history.md

The commit to be voted upon:

https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=0be8eaebcf27afae9ecda8ab79db63c214426561

Its hash is 0be8eaebcf27afae9ecda8ab79db63c214426561

Tag:
https://github.com/apache/calcite/tree/calcite-1.36.0-rc0

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.36.0-rc0
(revision 65079)

The hashes of the artifacts are as follows:

3bf003a87f76f2fa85b6af9b5243cddf67c767cb5caa828532784bd380e0d929da097677a453dc8d6a0d31f8cf97085031cf66b15a390571065b666095db3b80
*apache-calcite-1.36.0-src.tar.gz

A staged Maven repository is available for review at:

https://repository.apache.org/content/repositories/orgapachecalcite-1219/org/apache/calcite/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/libenchao.asc
https://www.apache.org/dist/calcite/KEYS

To create the jars and test Apache Calcite: "gradle build"
(requires an appropriate Gradle/JDK installation)

Please vote on releasing this package as Apache Calcite 1.36.0.

The vote is open for the next 72 hours and passes if a majority of at
least three +1 PMC votes are cast.

[ ] +1 Release this package as Apache Calcite 1.36.0
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...

Here is my vote:

+1 (binding)

--

Best,
Benchao Li

Re: [DISCUSS] State of the project 2023

[Francis Chuang]

Thank you, Stamatis, for being chair and leading the project for 2023.

I also agree that it's been a great year for Calcite as we've seen 3 
releases for Calcite so far. We have also added a significant amount of 
committers.


There have also been more reviewers for PRs and participants on the 
mailing lists, which is an improvement to issues identified in previous 
years.


I also agree that the documentation for Calcite on the website can be a 
bit confusing and sparse, however, I think this can be remedied by 
reworking the information architecture of the website, so that 
information is presented in a more bite-sized and digestible manner.


I am also excited about the possibility of automating the release 
process [1]. I have not had time to look into it further, but hopefully, 
we can have some discussions about this as a community next year. I 
believe implementing release automation will significantly reduce the 
amount of mechanical work to produce a release and can potentially 
increase our release velocity.


I look forward to another exciting year with a new chair next year and I 
am excited to see further developments for the project and the community.


Francis

[1] https://lists.apache.org/thread/qkstx4o9qw90fxzqcfnp69w33h7vw2yg

On 6/11/2023 8:24 pm, Stamatis Zampetakis wrote:

Thanks everyone for sharing your thoughts.

Indeed documentation is a common pain point especially with those
starting off with Calcite. However, over the past few years there are
more and more people publishing blogs, talks, and tutorials around
Calcite. I find it very helpful and I would definitely like to see
more improvements around this area.

As far as it concerns testing we can always do better and personally I
am a big fan of extending test coverage. There are many good ideas
around improvements in our JIRA backlog and I hope to see many of
those implemented over the next year.

Note that the PMC nomination period has ended. The PMC will proceed
with the vote on existing candidates in the following days.

Best,
Stamatis

On Thu, Oct 26, 2023 at 8:42 PM Ran Tao  wrote:


Really, totally agree with Mihai & Hongyu about documentation.

In fact, I have a similar problem.
The learning curve of calcite is indeed steep,  most of my learning comes
from source code.

Fortunately, we still have a relatively rich javadoc in the source code.
If there is no javadoc, I mostly rely on experience to guess a certain
field or a certain logic.
There are relatively few people around me who know about calcite.

Of course, now I try to ask questions on the mailing list,
but considering the asynchronous situation of the mailing list and the fact
that new-beginners may not be willing or comfortable to ask questions by
email, it may not always work.

If we have some documentation from simple to in-depth,
such as how to build a simple function, a rule, from parser to optimizer,
how to combine some basic components to complete the optimization of a
large SQL or even run it.
Slowly increase the depth so that it will be more friendly to new-beginners.

I can’t imagine that all new people would go directly to the source code to
see it.
There is still a certain threshold for this.
I hope that in the future we can have some documents that are progressive
from shallow to deep,
no matter what page or form they are provided.

hope the community will get better and better in the new year.


Best Regards,
Ran Tao
https://github.com/chucheng92


Hongyu Guo  于2023年10月27日周五 00:05写道：


Hi devs,

There is no doubt that Calcite boasts powerful capabilities, but the curve
of acquiring and learning calcite is quite steep. After studying Calcite
for a year, I have only gained a limited understanding of some of its
modules. Mihai is about to contribute several documents related to calcite,
which is truly exciting. Calcite is a treasure, and I hope there will be
more developer documentation next year to enable developers to quickly
grasp how to use calcite and how it works.

Secondly, Calcite supports a wide array of SQL syntax, but there are still
a few syntaxes that it does not cover. I hope that Calcite can be equipped
with more comprehensive SQL syntax parsing capabilities, which will be the
selling point that convinces more developers to opt for Calcite. I am
anticipating that Calcite will support more syntax next year, both standard
and non-standard, and I will continue to contribute in this direction.

Best,
Hongyu Guo

On Tue, Oct 24, 2023 at 3:16 AM  wrote:


Hello all,

Calcite is great! However, I think that there are several areas where the
project could do better:
- testing
- documentation
- legacy code cleanup

(1) Testing: Most of my work in Calcite so far has been about testing. I
have contributed the SqlLogicTest suite, which uncovers many bugs.

However,

I have not filed issues for any of these bugs, and I have not fixed any

of

these bugs either, since I have been very busy with other bugs I found
using other testing methods.  I 

Re: How about enable dependabot?

[Francis Chuang]

Perhaps refreshVersions [1] can be used.

[1] https://splitties.github.io/refreshVersions/

On 6/11/2023 7:54 am, Julian Hyde wrote:

I agree that we should be trying to stay on the most recent version of
our dependencies (with a few exceptions, such as JavaCC). Most of our
dependencies are mature libraries, and the latest version is more
likely to fix security problems than to introduce bugs.

However, I'm not sure that Dependabot is the best way to do it. One,
dependabot generates quite a lot of noise (frequent upgrades). Two, we
would have to restructure our build files. The best process is
probably to do manual upgrades, like
https://github.com/apache/calcite/pull/3504, just before each release.
Is there a straightforward way to script those upgrades?

Julian


On Sun, Nov 5, 2023 at 1:09 AM Jiajun Xie  wrote:


Hi, Hongyu.

Your idea is great and you also introduced the steps to use it.

We need more feedback about benefits and risks from calcite users.
# What are the benefits?
- Quickly fix dependency vulnerabilities.
- Balancing the workload of each upgrade(Not 4.0 to 7.x).
- ...

# What are the risks?
- The latest version may be unstable.
- The burden of upgrading Calcite for users has increased.
- ...

For me, the risks are acceptable.
I am willing to help you complete this work.

On Sat, 4 Nov 2023 at 21:04, Hongyu Guo  wrote:


Hi all,

Recently, I opened 2 PRs about removing an unused library[1] and bumping
various libraries[2]. I noticed that many dependencies of calcite are
outdated. To address this issue, I suggest enabling dependabot[3] to
automatically open "bump dependency" PRs and make calcite healthier.

If we enable dependabot, what should we do?

- Add `dependabot.yml` to `.github/`. It is straightforward, just follow
the instructions in the documentation[4].
- Refactor gradle project files: Dependabot's support for gradle is not
sufficient as it only reads the text of `build.gradle.kts`, `build.gradle`,
and `settings.gradle.kts` instead of running gradle. Additionally,
dependabot can NOT read `gradle.properties`, so we need to refactor the
gradle project files.
- Ignore some dependencies: Some dependencies cannot be upgraded. For
example, I attempted to bump javacc from 4.0 to 7.x, but due to
incompatibility caused by the large version span, I had to give up. Also,
we cannot upgrade elasticsearch due to licensing restrictions.

What is your opinion on dependabot?

[1]https://github.com/apache/calcite/pull/3502
[2]https://github.com/apache/calcite/pull/3504
[3]

https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates
[4]

https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#gradle

Best,
Hongyu

Re: [ANNOUNCE] New committer: Hongyu Guo

[Francis Chuang]

Congrats, Hongyu!

On 3/11/2023 2:09 am, LakeShen wrote:

Congratulations

Runkang He  于2023年11月2日周四 22:51写道：


Congratulations, Hongyu!

Best,
Runkang He

Benchao Li  于2023年11月2日周四 22:27写道：


Apache Calcite's Project Management Committee (PMC) has invited Hongyu
Guo to become a committer, and we are pleased to announce that he has
accepted.

Hongyu's contributions are around the functions, parser, DDL(CREATE
TABLE LIKE, GRANT, REVOKE), and simplication. Apart from the code
contribution, Hongyu is also very active in the mailing list and code
reviews.

Hongyu, welcome, thank you for your contributions, and we look forward
to your further interactions with the community! If you wish, please
feel free to tell us more about yourself and what you are working on.

As your first commit, please add yourself to the contributors list [1]
and the community page will re-generate [2].

Benchao Li (on behalf of the Apache Calcite PMC)

[1]
https://github.com/apache/calcite/blob/main/site/_data/contributors.yml
[2] https://calcite.apache.org/community/#project-members

--

Best,
Benchao Li

Re: [ANNOUNCE] New committer: Runkang He

[Francis Chuang]

Congrats, Runkang!

On 3/11/2023 3:54 am, Tanner Clary wrote:

Congratulations, Runkang!

Best,
Tanner

On Thu, Nov 2, 2023 at 9:11 AM Ran Tao  wrote:


Congrats, Runkang!

Best Regards,
Ran Tao


Benchao Li  于2023年11月2日周四 22:27写道：


Apache Calcite's Project Management Committee (PMC) has invited
Runkang He to become a committer, and we are pleased to announce that
they have accepted.

Runkang has added many new functions to Hive and Spark libraries, and
various improvements around simplification and sub-query. Apart from
code contributions, Runkang also helps a lot with code reviews.

Runkang, welcome, thank you for your contributions, and we look
forward to your further interactions with the community! If you wish,
please feel free to tell us more about yourself and what you are
working on.

As your first commit, please add yourself to the contributors list [1]
and the community page will re-generate [2].

Benchao Li (on behalf of the Apache Calcite PMC)

[1]
https://github.com/apache/calcite/blob/main/site/_data/contributors.yml
[2] https://calcite.apache.org/community/#project-members

--

Best,
Benchao Li

Re: [DISCUSS] Calcite Jenkins job fails due to Nexus account problem

[Francis Chuang]

The ASF release Gradle plugin requires those values to push to nexus.

It seems strange that it's trying to build and publish. Is it trying to 
build a nightly snapshot and publish it to Nexus? That could be why it's 
throwing up all of these errors.


To fix the error, we'll need to open a ticket with Infra to set those 
values, however, it'd be good to check if there's a GitHub Actions 
workflow doing the same thing, to avoid conflicts.



On 2/11/2023 4:20 pm, Benchao Li wrote:

Hi all,

I noticed that recently jobs are all failing[1][2] with the following
message, anyone knows why? Is there anything changed in Gradle
recently?

Please correct the following before proceeding with the release:
1) Project property 'asfNexusUsername' is not specified
2) Project property 'asfNexusPassword' is not specified

[1] https://ge.apache.org/s/w56jhscwxw5ei
[2] https://ge.apache.org/s/dbni4geb7yl7q

Re: [ANNOUNCE] New committer: Lei Shen

[Francis Chuang]

Congrats, Lei!

On 1/11/2023 4:34 am, Stamatis Zampetakis wrote:

Apache Calcite's Project Management Committee (PMC) has invited Lei Shen to
become a committer, and we are pleased to announce that they have accepted.

Lei has added many new optimizer rules to the project enhancing the
query plans for Calcite and downstream projects and pushed various
enhancements around the TABLESAMPLE clause. Apart from code
contributions, Lei is very active in the dev list participating in
discussions and helping a lot with reviews.

Lei, welcome, thank you for your contributions, and we look forward to your
further interactions with the community! If you wish, please feel free to tell
us more about yourself and what you are working on.

As your first commit, please add yourself to the contributors list [1]
and the community page will re-generate [2].

Stamatis (on behalf of the Apache Calcite PMC)

[1] https://github.com/apache/calcite/blob/main/site/_data/contributors.yml
[2] https://calcite.apache.org/community/#project-members

Re: [ANNOUNCE] New committer: Ran Tao

[Francis Chuang]

Congrats!

On 28/10/2023 11:32 am, Benchao Li wrote:

Congrats, Ran!

Runkang He  于2023年10月28日周六 07:34写道：


Congrats Ran!

Best,
Runkang He

Alessandro Solimando  于2023年10月28日周六
00:08写道：


Congrats Ran Tao and welcome!

On Fri, 27 Oct 2023 at 17:42, Ruben Q L  wrote:


Congrats!


On Fri, Oct 27, 2023 at 4:40 PM Tanner Clary 
wrote:


Congrats Ran!! Have learned a lot from your pull requests!

Best,
Tanner

On Fri, Oct 27, 2023 at 8:32 AM Stamatis Zampetakis 


wrote:


Apache Calcite's Project Management Committee (PMC) has invited Ran

Tao

to

become a committer, and we are pleased to announce that he has

accepted.


Ran has implemented numerous improvements and fixes in the past few
months. He has added new SQL functions to the Spark library,

addressed

various issues related to casts and type inference, enhanced
documentation, and made various changes with the aim of improving

code

quality

Ran, welcome, thank you for your contributions, and we look forward

to

your

further interactions with the community! If you wish, please feel

free

to

tell
us more about yourself and what you are working on.

As your first commit, please add yourself to the contributors list

[1]

and the community page will re-generate [2].

Stamatis (on behalf of the Apache Calcite PMC)

[1]


https://github.com/apache/calcite/blob/main/site/_data/contributors.yml

[2] https://calcite.apache.org/community/#project-members

Re: [ANNOUNCE] New committer: Mihai Budiu

[Francis Chuang]

Congrats, Mihai!

On 26/10/2023 7:56 pm, Stamatis Zampetakis wrote:

Apache Calcite's Project Management Committee (PMC) has invited Mihai
Budiu to become a committer, and we are pleased to announce that he
has accepted.

Mihai has addressed numerous compile and runtime issues in SQL
functions and has made several significant improvements to the test
infrastructure to enhance code coverage, quality, and stability. In
addition to code contributions, Mihai is highly active on the mailing
list, where he answers questions, assists others, and shares ideas for
future improvements. Mihai has also been writing blogs and giving
talks about Calcite at various events and conferences, showcasing
Calcite in both simple and more advanced use cases, which can greatly
contribute to the growth of the community.

Mihai, welcome, thank you for your contributions, and we look forward
to your further interactions with the community! If you wish, please
feel free to tell us more about yourself and what you are working on.

As your first commit, please add yourself to the contributors list [1]
and the community page will re-generate [2].

Stamatis (on behalf of the Apache Calcite PMC)

[1] https://github.com/apache/calcite/blob/main/site/_data/contributors.yml
[2] https://calcite.apache.org/community/#project-members

Re: Donation of "calcite-cli" Repository for Calcite SQL Prompt

[Francis Chuang]

Thanks for creating this project, Satya! It's great seeing projects 
built around Calcite to improve developer experience.


If we were to integrate the code into avatica-go, it should be done as a 
separate module. It would reside in it's folder, which following go 
conventions would be cmd/cli and have its own go.mod file.


The reason for this is that the cli pulls in its own dependencies 
(including avatica-go), but avatica-go does not use the same 
dependencies as the cli. In other words, if both the cli and avatica-go 
are in the same module, someone installing avatica-go would need to pull 
in unneeded dependencies.


In terms of releasing, things might be a bit more complicated. If the 
cli is its own separate module, then it should be able to have its own 
release schedule. For the git tag, it would be tagged as cmd/cli/vX.Y.Z. 
However, we ship a tar.gz containing the repository's contents as the 
release and it would contain the code for both avatica-go and the cli, 
even though the release might be for just avatica-go or just the cli. 
Not sure how this fits in with the ASF's release guidelines, so this 
will need a bit more exploration.


As for the JDBC equivalent in Go, that would be the database/sql package 
[1], of which avatica-go is a driver. From past experience, I have not 
seen a cli tool included with a database/sql driver, so if we were to 
keep with the "Go way" of doing things, then perhaps it's not the best 
idea to integrate the code into avatica-go.


The calcite-cli project includes calcite-specific features such as the 
built in list of keywords [2]. This is in contrast to a popular, general 
tool that works with all database/sql drivers: usql [3].


In my personal opinion, I think calcite-cli is an excellent project for 
the Calcite ecosystem. However, I feel that it would be better as an 
independent project, whether as a subproject under calcite or not, 
rather than integrating it into avatica-go, for the reasons aforementioned.


Francis

[1] https://pkg.go.dev/database/sql
[2] 
https://github.com/satyakommula96/calcite-cli/blob/main/prompt/completer.go

[3] https://github.com/xo/usql

On 16/10/2023 4:17 pm, Julian Hyde wrote:

This project seems to do a similar job to SQLLine, except that it is
written in Go rather than Java, and speaks the Avatica protocol rather
than JDBC.

A few observations:

1. The best fit for it would be in the avatica-go project. But SQLLine
has been successful as an independent project (not tied to any
particular back-end). The loose coupling has been successful for both
Calcite/Avatica and SQLLine. So, I wonder whether this could also be
successful as an independent project. Avatica-go could reference it,
in the same way that Calcite includes a bash script to launch SQLLine,
even though SQLLine is independently developed, versioned and
released.

(Hive forked SQLLine to create a utility, BeeLine, that is now part of
their source tree. In my opinion that was a mistake. It would have
been better if they had referenced SQLLine, and added hooks to
customize it.)

2. Would it be possible to make this CLI more loosely coupled? Maybe
it should depend on Go's equivalent of JDBC (sorry I'm no Go expert)
rather than directly on the Avatica API. Then it could be used as a
CLI to talk to other databases.

Julian







On Sun, Oct 15, 2023 at 8:01 AM Hongyu Guo  wrote:


Hi Satya,
I take a quick look for your repository, I'm not sure if your project has
already finished, I notice some .go file is empty, did you forget to push
some commits?

 From the current code, you have imported the calcite-avatica-go project and
provided a command line tool. I don't think you need to create a new
project, it would be better choice to submit the new feature you mentioned
in the form of a Pull Request to calcite-avatica.

You can log a new JIRA case first.

Best,
Hongyu Guo

Satya Kommula  于2023年10月15日周日 13:49写道：


Dear Apache Calcite Development Team,

I hope this message finds you well. I am writing to express my interest in
donating the "calcite-cli" repository, available at "
https://github.com/satyakommula96/calcite-cli; to the Apache Calcite
project. This repository provides a valuable SQL prompt for executing both
multiline and single-line queries, which aligns with the capabilities of
the Calcite project.
The "calcite-cli" repository has been developed with the aim of enhancing
the SQL querying experience by providing features that align with the
principles and objectives of Apache Calcite. It enables users to work with
complex queries, offering both multiline and single-line query support,
which is crucial for a wide range of use cases.
I believe that integrating "calcite-cli" with the Apache Calcite project
would be mutually beneficial. It would provide the Calcite community with a
valuable tool for query execution and testing, and it would allow me to
contribute to the ongoing development and improvement of Apache Calcite. I
am committed to supporting and 

Re: Draft: board report for 2023 Q3

[Francis Chuang]

+1, Excellent work, Stamatis!

On 2/10/2023 6:58 pm, Stamatis Zampetakis wrote:

Hello,

Below you can find a draft of this quarter's board report. I plan to
submit the final version next Monday (October 9, 2023).

Please let me know if you have any additions or corrections.

Best,
Stamatis
---

## 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.

## Project Status:
Current project status: ongoing
Issues for the board: none

## Membership Data:
Apache Calcite was founded 2015-10-22 (8 years ago)
There are currently 69 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Benchao Li on 2023-01-27.
- TJ Banghart was added as committer on 2023-07-04
- Dan Zou was added as committer on 2023-07-04

## Project Activity:
Apache Calcite 1.35.0 was released on 2023-07-26. It contains contributions
from 36 contributors, and resolves 140 issues. The new release has many
improvements in the BigQuery and Spark dialect bringing in more than 40 SQL
functions. Additionally, it comes with new optimizations for reducing the size
of generated code and more powerful expression simplifications.

On August 18, 2023, Benchao Li and Jiajun Xie represented the Calcite
community at the Apache Con East Asia by giving talks related with the
project.

## Community Health:
The project is healthy. Previously, it was super healthy. The drop is likely
to the fact that the PMC has not grown in the last six months but this will
very likely change in the near future since a lot of our current committers
are very involved with the project and hopefully they will join the PMC
shortly.

The dev list had a 38% in activity in the past quarter, with busiest threads
been as usual those around releases and introduction of new committers. The
16% increase in activity of the JIRA also contributes to the general increase
in traffic of the dev list.

The number of non-committer (contributor) commits per month:
+-+-+-+
|year |month| contributor_commits |
+-+-+-+
| 2023| 7   | 16  |
| 2023| 8   | 32  |
| 2023| 9   | 32  |
+-+-+-+

The number of active reviewers per month:
+-+-+-+
|year |month|  active_reviewers   |
+-+-+-+
| 2023| 7   | 9   |
| 2023| 8   | 9   |
| 2023| 9   | 10  |
+-+-+-+

Top-3 reviewers in the last quarter:
+---+-+
| committer |   reviews   |
+---+-+
| Jiajun  | 15  |
| Julian Hyde  | 13  |
| Benchao Li  | 11  |
+---+-+

The number of non-committer commits has increased by 9% from the last quarter
(73 commits in Q2 vs. 80 commits in Q3) keeping up the good momentum of having
new people contributing to the project.

The average number of active reviewers per month has increased slightly from
the last quarter (7.6 in Q2 vs. 9.3 in Q3) showing that more people are
participating in the review process which is among the main points of the
project.

In the top reviewers, we can observe that things are a bit more balanced in
Q3. The review count per person in the top-3 tier is lower than usual but in
conjunction with the increase in the number of non-committer commits
it shows that
reviews are more evenly distributed among the members of the community.

Re: PR CI Failures Question

[Francis Chuang]

There's a "Calcite Committers" team on Github and I am assuming anyone 
who is a Calcite committer would be automatically to the team and they 
should be able to clear cache entries.


On 1/09/2023 7:40 pm, Alessandro Solimando wrote:

Thanks Francis,
I do see the trash can icons too, haven't tried to click on any but I guess
I have permissions.

On Fri, 1 Sept 2023 at 11:36, Francis Chuang 
wrote:


GitHub Action's caches are here:
https://github.com/apache/calcite/actions/caches

For me, there's a trash can icon next to each entry to delete each cache
entry.

On 1/09/2023 7:32 pm, Alessandro Solimando wrote:

Question to Francis, how do you clear the Gradle cache?

Would it make sense to share the steps in
https://calcite.apache.org/develop/#contributing?

I am asking because we already suggest how to retrigger CI by "git commit
--allow-empty" in that page.

If clearing the cache requires some special permissions, we can specify

it,

but it will be a good reference for whoever has those permissions.

Best regards,
Alessandro

On Fri, 1 Sept 2023 at 04:40, Ran Tao  wrote:


I also encountered this problem once, even force-push didn't work.
I recreated PR to bypass this problem. It also happened on windows.

https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-5878

Best Regards,
Ran Tao


Tanner Clary  于2023年9月1日周五 00:15写道：


Hi Calcite Developers,

I have a PR [1] that is failing the CI checks for Windows [2]. I am not
familiar with these errors and am wondering if anyone has any

suggestions

on how I could fix them. Thanks so much.

Best,
Tanner Clary

[1] https://github.com/apache/calcite/pull/3391
[2]




https://github.com/apache/calcite/actions/runs/6039592258/job/16388593881

Re: PR CI Failures Question

[Francis Chuang]

GitHub Action's caches are here: 
https://github.com/apache/calcite/actions/caches


For me, there's a trash can icon next to each entry to delete each cache 
entry.


On 1/09/2023 7:32 pm, Alessandro Solimando wrote:

Question to Francis, how do you clear the Gradle cache?

Would it make sense to share the steps in
https://calcite.apache.org/develop/#contributing?

I am asking because we already suggest how to retrigger CI by "git commit
--allow-empty" in that page.

If clearing the cache requires some special permissions, we can specify it,
but it will be a good reference for whoever has those permissions.

Best regards,
Alessandro

On Fri, 1 Sept 2023 at 04:40, Ran Tao  wrote:


I also encountered this problem once, even force-push didn't work.
I recreated PR to bypass this problem. It also happened on windows.

https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-5878

Best Regards,
Ran Tao


Tanner Clary  于2023年9月1日周五 00:15写道：


Hi Calcite Developers,

I have a PR [1] that is failing the CI checks for Windows [2]. I am not
familiar with these errors and am wondering if anyone has any suggestions
on how I could fix them. Thanks so much.

Best,
Tanner Clary

[1] https://github.com/apache/calcite/pull/3391
[2]


https://github.com/apache/calcite/actions/runs/6039592258/job/16388593881

Re: PR CI Failures Question

[Francis Chuang]

I deleted the caches for the PR in GitHub Actions and retriggered the 
job. It looks like its running now.


Francis

On 1/09/2023 7:41 am, Julian Hyde wrote:

Actually, no need to force-push, just restart the job.


On Aug 31, 2023, at 2:41 PM, Julian Hyde  wrote:

I searched for the error message and it’s maybe a corrupted Gradle cache. That 
sounds plausible, because the message doesn’t look specific to Windows or your 
change. Just one container gone bad. I’d force-push and see whether I get a 
healthier container next run.

Julian

[1] 
https://stackoverflow.com/questions/65645510/cannot-access-script-base-class-org-gradle-kotlin-dsl-kotlinbuildscript


On Aug 31, 2023, at 9:13 AM, Tanner Clary  
wrote:

Hi Calcite Developers,

I have a PR [1] that is failing the CI checks for Windows [2]. I am not
familiar with these errors and am wondering if anyone has any suggestions
on how I could fix them. Thanks so much.

Best,
Tanner Clary

[1] https://github.com/apache/calcite/pull/3391
[2]
https://github.com/apache/calcite/actions/runs/6039592258/job/16388593881

Re: PR CI Failures Question

[Francis Chuang]

I just retriggered the job to see if it passes. Alessandro retriggered 
it a few hours ago and it was still  failing. Perhaps we need to clear 
the cache in GitHub Actions.


Francis

On 1/09/2023 7:41 am, Julian Hyde wrote:

Actually, no need to force-push, just restart the job.


On Aug 31, 2023, at 2:41 PM, Julian Hyde  wrote:

I searched for the error message and it’s maybe a corrupted Gradle cache. That 
sounds plausible, because the message doesn’t look specific to Windows or your 
change. Just one container gone bad. I’d force-push and see whether I get a 
healthier container next run.

Julian

[1] 
https://stackoverflow.com/questions/65645510/cannot-access-script-base-class-org-gradle-kotlin-dsl-kotlinbuildscript


On Aug 31, 2023, at 9:13 AM, Tanner Clary  
wrote:

Hi Calcite Developers,

I have a PR [1] that is failing the CI checks for Windows [2]. I am not
familiar with these errors and am wondering if anyone has any suggestions
on how I could fix them. Thanks so much.

Best,
Tanner Clary

[1] https://github.com/apache/calcite/pull/3391
[2]
https://github.com/apache/calcite/actions/runs/6039592258/job/16388593881

Re: Main Code freeze is over and commits can resume

[Francis Chuang]

Thanks for shepherding 1.35.0 and getting it released. Excellent work, 
Xiong!


On 27/07/2023 8:51 pm, Xiong Duan wrote:

Hello Calcite Community,

  We have released Calcite 1.35.0, The Main Code freeze is over and
commits can resume.

Best,
Xiong Duan

Re: [VOTE] Release Apache Calcite 1.35.0 (release candidate 3)

[Francis Chuang]

My vote is: +1 (binding)

- Verified GPG signature - OK
- Verified SHA512 - OK
- Diffed source release and git repository - OK
- Checked release notes on tag 
(https://github.com/apache/calcite/blob/calcite-1.35.0-rc3/site/_docs/history.md) 
- OK

- Checked year and versions in NOTICE, README and HOWTO - OK
- Ran tests (gradle check) - OK
- Spot checked Nexus artifacts - OK

Environment:
Eclipse-temurin:19-jammy docker container in WSL2 (Ubuntu 22.04.2) on 
Windows 11 22h2


$ docker version
Client: Docker Engine - Community
 Cloud integration: v1.0.35
 Version:   24.0.2
 API version:   1.43
 Go version:go1.20.4
 Git commit:cb74dfc
 Built: Thu May 25 21:52:17 2023
 OS/Arch:   linux/amd64
 Context:   default

Server: Docker Desktop
 Engine:
  Version:  24.0.2
  API version:  1.43 (minimum version 1.12)
  Go version:   go1.20.4
  Git commit:   659604f
  Built:Thu May 25 21:52:17 2023
  OS/Arch:  linux/amd64
  Experimental: false
 containerd:
  Version:  1.6.21
  GitCommit:3dce8eb055cbb6872793272b4f20ed16117344f8
 runc:
  Version:  1.1.7
  GitCommit:v1.1.7-0-g860f061
 docker-init:
  Version:  0.19.0
  GitCommit:de40ad0

$ gradle -v


Gradle 7.6.1


Build time:   2023-02-24 13:54:42 UTC
Revision: 3905fe8ac072bbd925c70ddbf4463341f4b4

Kotlin:   1.7.10
Groovy:   3.0.13
Ant:  Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM:  19.0.2 (Eclipse Adoptium 19.0.2+7)
OS:   Linux 5.15.90.1-microsoft-standard-WSL2 amd64

$ java --version
openjdk 19.0.2 2023-01-17
OpenJDK Runtime Environment Temurin-19.0.2+7 (build 19.0.2+7)
OpenJDK 64-Bit Server VM Temurin-19.0.2+7 (build 19.0.2+7, mixed mode, 
sharing)


Francis

On 22/07/2023 9:40 am, Xiong Duan wrote:

Hi all,


I have created a build for Apache Calcite 1.35.0, release

candidate 3.


Thanks to everyone who has contributed to this release.


You can read the release notes here:

https://github.com/apache/calcite/blob/calcite-1.35.0-rc3/site/_docs/history.md


The commit to be voted upon:

https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=75750b78b5ac692caa654f506fc1515d4d3991d6


Its hash is 75750b78b5ac692caa654f506fc1515d4d3991d6


Tag:

https://github.com/apache/calcite/tree/calcite-1.35.0-rc3


The artifacts to be voted on are located here:

https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.35.0-rc3

(revision 63131)


The hashes of the artifacts are as follows:

a19e0e73dfaa4d54d4d27db24c1b5674979e5461ed4c0bd1408aaec72ff82e832b3e4dee13c9d6552d3b5a9db86c1f11b9a960521e76dd65fc661565e160f63e

*apache-calcite-1.35.0-src.tar.gz


A staged Maven repository is available for review at:

https://repository.apache.org/content/repositories/orgapachecalcite-1216/org/apache/calcite/


Release artifacts are signed with the following key:

https://people.apache.org/keys/committer/xiong.asc

https://www.apache.org/dist/calcite/KEYS


To create the jars and test Apache Calcite: "gradle build"

(requires an appropriate Gradle/JDK installation)


Please vote on releasing this package as Apache Calcite 1.35.0.


The vote is open for the next 72 hours and passes if a majority of at least
three +1 PMC votes are cast.


[ ] +1 Release this package as Apache Calcite 1.35.0

[ ]  0 I don't feel strongly about it, but I'm okay with the release

[ ] -1 Do not release this package because...


Here is my vote:


+1 (binding)


Best,
Xiong Duan

Re: [VOTE] Release Apache Calcite 1.35.0 (release candidate 2)

[Francis Chuang]

+1 as this is a regression. Thanks, Gian, for discovering this.

On 20/07/2023 6:36 pm, Ruben Q L wrote:

Thanks Gian for signaling this issue.

Since this is a regression introduced in 1.35 (and it looks more or less
simple to fix) IMO we should cancel the rc2 vote, fix CALCITE-5865 and move
to a rc3.

Best,
Ruben



On Thu, Jul 20, 2023 at 3:29 AM Chunwei Lei  wrote:


Thanks Xiong Duan for being RM for this release.


- Checked release notes on tag: some comments


Some improvements in simplify an expression.

Some improvements in simplifying an expression.


[CALCITE-5717] RelBuilder.project of literals on a single-row `Aggregate`

should create a Values
I think Aggregate should not be quoted since other operators are not quoted
either.


- Checksum: ok
- Signature: ok
- Diff source release and git repository: ok
- Build + tests: ok




Best,
Chunwei


On Thu, Jul 20, 2023 at 7:26 AM Gian Merlino  wrote:


When testing this with Apache Druid we found a problem: the change in
CALCITE-5747 broke a few of our test cases due to this piece:


https://github.com/apache/calcite/pull/3245/files#diff-e873041549333502af52ece8a1b34301ae5a059ff4719e9bddbaef48929e7047L7338-L7341


Essentially, FLOOR and CEIL no longer work with a SqlConformance that is
not a SqlConformanceEnum. (In Druid we have a conformance that extends
SqlAbstractConformance.)

I wrote up a Jira case here:
https://issues.apache.org/jira/browse/CALCITE-5865, and have a patch up
here: https://github.com/apache/calcite/pull/3327

Could we include this fix in 1.35.0? Arguably, since this would be a new
problem in 1.35.0, it should be fixed prior to release.

On 2023/07/17 18:24:21 xiong duan wrote:

Hi all,


I have created a build for Apache Calcite 1.35.0, release

candidate 2.


Thanks to everyone who has contributed to this release.


You can read the release notes here:





https://github.com/apache/calcite/blob/calcite-1.35.0-rc2/site/_docs/history.md



The commit to be voted upon:





https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=2f5635f13a4eb4b89c119fabf25b1d31e0018426



Its hash is 2f5635f13a4eb4b89c119fabf25b1d31e0018426


Tag:

https://github.com/apache/calcite/tree/calcite-1.35.0-rc2


The artifacts to be voted on are located here:



https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.35.0-rc2


(revision 63046)


The hashes of the artifacts are as follows:





b5d837e3725554254bdad0e4f4a63134193a1e3f44bb9b862d9eeeb7f9a5e9bae01985e2f1857874928dc4dbf1f4ca3ae4debacc096470081c249eba699dc74e


*apache-calcite-1.35.0-src.tar.gz


A staged Maven repository is available for review at:





https://repository.apache.org/content/repositories/orgapachecalcite-1213/org/apache/calcite/



Release artifacts are signed with the following key:

https://people.apache.org/keys/committer/xiong.asc

https://www.apache.org/dist/calcite/KEYS


To create the jars and test Apache Calcite: "gradle build"

(requires an appropriate Gradle/JDK installation)


Please vote on releasing this package as Apache Calcite 1.35.0.


The vote is open for the next 72 hours and passes if a majority of at

least three +1 PMC votes are cast.


[ ] +1 Release this package as Apache Calcite 1.35.0

[ ]  0 I don't feel strongly about it, but I'm okay with the release

[ ] -1 Do not release this package because...


Here is my vote:


+1 (binding)

Re: Signing releases using automated release infra

[Francis Chuang]

According to [1], infra is exploring uploading artifacts from CI, so 
there's a possibility we can do this in the future.


Regarding closing the nexus repository, we already automate this when 
running `./gradlew prepareVote`, so given that infra can give CI access 
to the nexus repository, we can already automate this.


I'll definitely be keeping an eye on the thread on dev@community and 
once the pieces are all available, we can discuss on vote here to see 
how we want to proceed :)


[1] https://lists.apache.org/thread/h4pkrnlygygb1mdyncnvw74xzrzls9ww

On 19/07/2023 8:11 pm, Stamatis Zampetakis wrote:

If I remember well it is intentional that some part of the process
(svn upload, nexus close, etc.) is not fully automated and explicitly
requires human intervention for legal purposes.

Best,
Stamatis


On Wed, Jul 19, 2023 at 12:13 PM Francis Chuang
 wrote:


Thanks for bringing this to our attention, Stamatis.

This is definitely a huge step forward and something I'd love to see
implemented for all Calcite projects.

The only downside at the moment is that the artifacts are not
automatically uploaded to dist.a.o svn server. The way log4j implemented
their workflow is for the RM to download those artifacts from GitHub and
upload them manually. This can probably be implemented using a script
that the RM would run locally on their system, but isn't ideal.

I will reply to that thread to see if there's some possibility of
automating the uploading of artifacts to svn via CI as well.

For me, the ideal release process would be to completely eliminate all
mechanical steps in the release process. The ideal release process would
be for the RM to only deal with the people and project management side
of things, e.g.

1. RM opens a PR containing changes to the changelog and dates in the
NOTICE and LICENSE files, etc.
2. RM shepherds PRs and other changes to the release and gets them
committed in main.
3. Contributors can comment on the PR for the release with suggestions,
etc for the changelog.
4. Once the rc is ready, the PR is merged and an rc release is tagged.
5. CI picks up the tag and automatically builds and uploads all release
artifacts. The vote email is automatically generated in CI, which the RM
sends to the list.
6. RM tallys votes and if the vote fails, builds the next RC, starting
from step 1.
7. If the vote passes, RM tags a final release.
8. CI picks up the tag and automatically build and signs artifacts.
9. RM announces to the list and updates the website announcing the release.

Francis

On 19/07/2023 6:43 pm, Stamatis Zampetakis wrote:

Hello,

Allowing CI to automate part of the release process is now approved by
LEGAL and some projects are already taking advantage of it. For more
information check out the respective thread [1].

The Calcite release preparation is quite automated already so we may
not really need this at this point but sharing the news since it is a
topic that has been discussed a lot in ASF the past few years.

Best,
Stamatis

[1] https://lists.apache.org/thread/y5b375054p1yjb2yprnnt16bt4qyccc2

Re: Signing releases using automated release infra

[Francis Chuang]

Thanks for bringing this to our attention, Stamatis.

This is definitely a huge step forward and something I'd love to see 
implemented for all Calcite projects.


The only downside at the moment is that the artifacts are not 
automatically uploaded to dist.a.o svn server. The way log4j implemented 
their workflow is for the RM to download those artifacts from GitHub and 
upload them manually. This can probably be implemented using a script 
that the RM would run locally on their system, but isn't ideal.


I will reply to that thread to see if there's some possibility of 
automating the uploading of artifacts to svn via CI as well.


For me, the ideal release process would be to completely eliminate all 
mechanical steps in the release process. The ideal release process would 
be for the RM to only deal with the people and project management side 
of things, e.g.


1. RM opens a PR containing changes to the changelog and dates in the 
NOTICE and LICENSE files, etc.
2. RM shepherds PRs and other changes to the release and gets them 
committed in main.
3. Contributors can comment on the PR for the release with suggestions, 
etc for the changelog.

4. Once the rc is ready, the PR is merged and an rc release is tagged.
5. CI picks up the tag and automatically builds and uploads all release 
artifacts. The vote email is automatically generated in CI, which the RM 
sends to the list.
6. RM tallys votes and if the vote fails, builds the next RC, starting 
from step 1.

7. If the vote passes, RM tags a final release.
8. CI picks up the tag and automatically build and signs artifacts.
9. RM announces to the list and updates the website announcing the release.

Francis

On 19/07/2023 6:43 pm, Stamatis Zampetakis wrote:

Hello,

Allowing CI to automate part of the release process is now approved by
LEGAL and some projects are already taking advantage of it. For more
information check out the respective thread [1].

The Calcite release preparation is quite automated already so we may
not really need this at this point but sharing the news since it is a
topic that has been discussed a lot in ASF the past few years.

Best,
Stamatis

[1] https://lists.apache.org/thread/y5b375054p1yjb2yprnnt16bt4qyccc2

Re: [VOTE] Release Apache Calcite 1.35.0 (release candidate 2)

[Francis Chuang]

Thanks for being RM for this release, Xiong!

My vote is: +1 (binding)

- Verified GPG signature - OK
- Verified SHA512 - OK
- Diffed source release and git repository - OK
- Checked release notes on tag 
(https://github.com/apache/calcite/blob/calcite-1.35.0-rc2/site/_docs/history.md) 
- OK

- Checked year and versions in NOTICE, README and HOWTO - OK
- Ran tests (gradle check) - OK
- Spot checked Nexus artifacts - OK

Environment:
Eclipse-temurin:19-jammy docker container in WSL2 (Ubuntu 22.04.2) on 
Windows 11 22h2


$ docker version
Client: Docker Engine - Community
 Cloud integration: v1.0.35
 Version:   24.0.2
 API version:   1.43
 Go version:go1.20.4
 Git commit:cb74dfc
 Built: Thu May 25 21:52:17 2023
 OS/Arch:   linux/amd64
 Context:   default

Server: Docker Desktop
 Engine:
  Version:  24.0.2
  API version:  1.43 (minimum version 1.12)
  Go version:   go1.20.4
  Git commit:   659604f
  Built:Thu May 25 21:52:17 2023
  OS/Arch:  linux/amd64
  Experimental: false
 containerd:
  Version:  1.6.21
  GitCommit:3dce8eb055cbb6872793272b4f20ed16117344f8
 runc:
  Version:  1.1.7
  GitCommit:v1.1.7-0-g860f061
 docker-init:
  Version:  0.19.0
  GitCommit:de40ad0

$ gradle -v


Gradle 7.6.1


Build time:   2023-02-24 13:54:42 UTC
Revision: 3905fe8ac072bbd925c70ddbf4463341f4b4

Kotlin:   1.7.10
Groovy:   3.0.13
Ant:  Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM:  19.0.2 (Eclipse Adoptium 19.0.2+7)
OS:   Linux 5.15.90.1-microsoft-standard-WSL2 amd64

$ java --version
openjdk 19.0.2 2023-01-17
OpenJDK Runtime Environment Temurin-19.0.2+7 (build 19.0.2+7)
OpenJDK 64-Bit Server VM Temurin-19.0.2+7 (build 19.0.2+7, mixed mode, 
sharing)


Francis

On 18/07/2023 4:24 am, xiong duan wrote:

Hi all,


I have created a build for Apache Calcite 1.35.0, release

candidate 2.


Thanks to everyone who has contributed to this release.


You can read the release notes here:

https://github.com/apache/calcite/blob/calcite-1.35.0-rc2/site/_docs/history.md


The commit to be voted upon:

https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=2f5635f13a4eb4b89c119fabf25b1d31e0018426


Its hash is 2f5635f13a4eb4b89c119fabf25b1d31e0018426


Tag:

https://github.com/apache/calcite/tree/calcite-1.35.0-rc2


The artifacts to be voted on are located here:

https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.35.0-rc2

(revision 63046)


The hashes of the artifacts are as follows:

b5d837e3725554254bdad0e4f4a63134193a1e3f44bb9b862d9eeeb7f9a5e9bae01985e2f1857874928dc4dbf1f4ca3ae4debacc096470081c249eba699dc74e

*apache-calcite-1.35.0-src.tar.gz


A staged Maven repository is available for review at:

https://repository.apache.org/content/repositories/orgapachecalcite-1213/org/apache/calcite/


Release artifacts are signed with the following key:

https://people.apache.org/keys/committer/xiong.asc

https://www.apache.org/dist/calcite/KEYS


To create the jars and test Apache Calcite: "gradle build"

(requires an appropriate Gradle/JDK installation)


Please vote on releasing this package as Apache Calcite 1.35.0.


The vote is open for the next 72 hours and passes if a majority of at

least three +1 PMC votes are cast.


[ ] +1 Release this package as Apache Calcite 1.35.0

[ ]  0 I don't feel strongly about it, but I'm okay with the release

[ ] -1 Do not release this package because...


Here is my vote:


+1 (binding)

Re: [VOTE] Release Apache Calcite 1.35.0 (release candidate 2)

[Francis Chuang]

Xiong,

Your committer key doesn't exist. Visiting 
https://people.apache.org/keys/committer/xiong.asc returns a 404.


Can you check to see if you've added the fingerprint to your LDAP 
profile? Instructions here: 
https://infra.apache.org/new-committers-guide.html#set-up-security-and-pgp-keys


I am unable to verify the release as I am unable to import your key via 
the ASF's committer key index into GPG.


Francis

On 18/07/2023 4:24 am, xiong duan wrote:

Hi all,


I have created a build for Apache Calcite 1.35.0, release

candidate 2.


Thanks to everyone who has contributed to this release.


You can read the release notes here:

https://github.com/apache/calcite/blob/calcite-1.35.0-rc2/site/_docs/history.md


The commit to be voted upon:

https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=2f5635f13a4eb4b89c119fabf25b1d31e0018426


Its hash is 2f5635f13a4eb4b89c119fabf25b1d31e0018426


Tag:

https://github.com/apache/calcite/tree/calcite-1.35.0-rc2


The artifacts to be voted on are located here:

https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.35.0-rc2

(revision 63046)


The hashes of the artifacts are as follows:

b5d837e3725554254bdad0e4f4a63134193a1e3f44bb9b862d9eeeb7f9a5e9bae01985e2f1857874928dc4dbf1f4ca3ae4debacc096470081c249eba699dc74e

*apache-calcite-1.35.0-src.tar.gz


A staged Maven repository is available for review at:

https://repository.apache.org/content/repositories/orgapachecalcite-1213/org/apache/calcite/


Release artifacts are signed with the following key:

https://people.apache.org/keys/committer/xiong.asc

https://www.apache.org/dist/calcite/KEYS


To create the jars and test Apache Calcite: "gradle build"

(requires an appropriate Gradle/JDK installation)


Please vote on releasing this package as Apache Calcite 1.35.0.


The vote is open for the next 72 hours and passes if a majority of at

least three +1 PMC votes are cast.


[ ] +1 Release this package as Apache Calcite 1.35.0

[ ]  0 I don't feel strongly about it, but I'm okay with the release

[ ] -1 Do not release this package because...


Here is my vote:


+1 (binding)

Re: [VOTE] Release Apache Calcite 1.35.0 (release candidate 0)

[Francis Chuang]

Hey Xiong Duan,

Can you send a cancellation message to the list to officially cancel the 
vote for rc0 by sending a [CANCEL] message?


Example here: 
https://lists.apache.org/thread/mdvdo67jmmt2ntxyom7s1c98kq9yf11y


Francis

On 18/07/2023 4:31 am, xiong duan wrote:

Thanks for your review, Looks like the URL is still in time to update. For
other problems, I have created RC2.

Julian Hyde  于2023年7月16日周日 22:48写道：


I don’t think the short links are an improvement to the vote email.

The release notes could be improved. I think CONVERT counts as a new
feature. Puffin and PairList do not (they’re utility classes).

There are so many new functions this time, how about adding a new section,
and sorting them alphabetically?

Can you convert contributors names to first last name? E.g. rubenql
appeared in previous releases as Ruben Quesada Lopez.

Julian


On Jul 14, 2023, at 7:33 AM, xiong duan  wrote:

Hi all,


I have created a build for Apache Calcite 1.35.0, release

candidate 0.


Thanks to everyone who has contributed to this release.


You can read the release notes here:

https://s.apache.org/p3rl9


The commit to be voted upon:

https://s.apache.org/8io6t


Its hash is bd4cac4ee30b4c275f5a229eb1704524c3dbc376


Tag:

https://github.com/apache/calcite/tree/calcite-1.35.0-rc0


The artifacts to be voted on are located here:

https://s.apache.org/c95f1

(revision 62985)


The hashes of the artifacts are as follows:



b2eb9b25727d1213f889e8d1a547a1f84c66af3821523ebe19a36ae5bc595daa74b4b4584914012bffca0a24be19a523c45dbaf72064d90f50feffc0de8a5e6e


*apache-calcite-1.35.0-src.tar.gz


A staged Maven repository is available for review at:



https://repository.apache.org/content/repositories/orgapachecalcite-1206/org/apache/calcite/



Release artifacts are signed with the following key:

https://people.apache.org/keys/committer/xiong.asc

https://www.apache.org/dist/calcite/KEYS


To create the jars and test Apache Calcite: "gradle build"

(requires an appropriate Gradle/JDK installation)


Please vote on releasing this package as Apache Calcite 1.35.0.


The vote is open for the next 72 hours and passes if a majority of at

least three +1 PMC votes are cast.


[ ] +1 Release this package as Apache Calcite 1.35.0

[ ]  0 I don't feel strongly about it, but I'm okay with the release

[ ] -1 Do not release this package because...


Here is my vote:


+1 (binding)

[jira] [Created] (CALCITE-5854) Test against Go 1.19 and 1.20

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-5854:
---

 Summary: Test against Go 1.19 and 1.20
 Key: CALCITE-5854
 URL: https://issues.apache.org/jira/browse/CALCITE-5854
 Project: Calcite
  Issue Type: New Feature
  Components: avatica-go
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: avatica-go-5.3.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (CALCITE-5853) Use HBase Phoenix images from GitHub container registry

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-5853:
---

 Summary: Use HBase Phoenix images from GitHub container registry
 Key: CALCITE-5853
 URL: https://issues.apache.org/jira/browse/CALCITE-5853
 Project: Calcite
  Issue Type: New Feature
  Components: avatica-go
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: avatica-go-5.3.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Draft: board report for 2023 Q2

[Francis Chuang]

+1, excellent work, Stamatis!

On 4/07/2023 9:04 pm, Ruben Q L wrote:

+1
Thanks Stamatis for preparing it!

On Tue, Jul 4, 2023 at 10:18 AM Stamatis Zampetakis 
wrote:


Hello,

Below you can find a draft of this quarter's board report. I plan to
submit it next Tuesday (July 11, 2023).
Please let me know if you have any additions or corrections.

Best regards,
Stamatis
-

## 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.

## Project Status:
Current project status: ongoing
Issues for the board: none

## Membership Data:
Apache Calcite was founded 2015-10-22 (8 years ago)
There are currently 67 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Benchao Li on 2023-01-27.
- Jacky Lau was added as committer on 2023-06-28
- Oliver Lee was added as committer on 2023-06-13
- Tanner Clary was added as committer on 2023-05-25
- Zhe Hu was added as committer on 2023-06-28

## Project Activity:
There were no releases during this quarter. The last release was Apache
Calcite 1.34.0 on 2023-03-14.

We are actively working towards Apache Calcite 1.35.0 and we plan to
release
the new version during July 2023.

On 2023-06-29, the Calcite community organised a Virtual key signing party
for
expanding the Web of trust and empowering the cryptographic signatures of
our
members and future release managers. 4 PMC members and 2 committers
attended
the event.

## Community Health:
The project remains super healthy.

The traffic in JIRA, GitHub, issues@, commits, has increased overall,
while
dev@ has dropped by 18%. During this quarter there were more discussions
and
exchanges under specific issues/tickets shifting the traffic from dev@ to
issues@ and other places.

The number of non-committer (contributor) commits per month:
+-+-+-+
|year |month| contributor_commits |
+-+-+-+
| 2023| 4   | 17  |
| 2023| 5   | 21  |
| 2023| 6   | 35  |
+-+-+-+

The number of active reviewers per month:
+-+-+-+
|year |month|  active_reviewers   |
+-+-+-+
| 2023| 4   | 6   |
| 2023| 5   | 6   |
| 2023| 6   | 11  |
+-+-+-+

Top-3 reviewers in the last quarter:
+---+-+
| committer |   reviews   |
+---+-+
| Julian Hyde  | 28  |
| Benchao Li  | 12  |
| rubenada  | 8   |
| Jiajun  | 8   |
+---+-+

The number of non-committer commits has increased roughly by 43% from the
last
quarter (51 commits in Q1 vs. 73 commits in Q2) which is promising for
inviting new committers in the near term.

The number of active reviewers increased slightly compared to the last
quarter
with June being the most active month for everyone. The preparation for the
1.35.0 release and the call for action did help in bringing those numbers
up
during June.

In terms of sharing the review load, things are a bit better this quarter
but
still far from being completely balanced. There have been discussions
around
the topic in the last quarter but we obviously need more involvement from
the
community members.

Re: [ANNOUNCE] New committer: TJ Banghart

[Francis Chuang]

Congrats, TJ!

On 4/07/2023 5:17 pm, Stamatis Zampetakis wrote:

Apache Calcite's Project Management Committee (PMC) has invited TJ Banghart to
become a committer, and we are pleased to announce that they have accepted.

TJ has been contributing to the community for about a year now. They
introduced many new SQL functions for parsing and formatting dates,
times, and timestamps extending the capabilities of the BigQuery
dialect. Furthermore, they pushed various improvements around JSON
serialization and deserialization, JDBC metadata, and lexical
policies.

TJ, welcome, thank you for your contributions, and we look forward to your
further interactions with the community! If you wish, please feel free to tell
us more about yourself and what you are working on.

As your first commit, please add yourself to the contributors list [1]
and the community page will re-generate [2].

Stamatis (on behalf of the Apache Calcite PMC)

[1] https://github.com/apache/calcite/blob/main/site/_data/contributors.yml
[2] https://calcite.apache.org/community/#project-members

Re: [ANNOUNCE] New committer: Dan Zou

[Francis Chuang]

Congrats, Dan!

On 4/07/2023 5:16 pm, Stamatis Zampetakis wrote:

Apache Calcite's Project Management Committee (PMC) has invited Dan Zou to
become a committer, and we are pleased to announce that they have accepted.

Dan has been doing some great work for the project over the past few
months. They implemented and enabled multiple new SQL functions for
BigQuery and MSSQL dialects, fixed some optimization rules, and
improved documentation and test code.

Dan, welcome, thank you for your contributions, and we look forward to your
further interactions with the community! If you wish, please feel free to tell
us more about yourself and what you are working on.

As your first commit, please add yourself to the contributors list [1]
and the community page will re-generate [2].

Stamatis (on behalf of the Apache Calcite PMC)

[1] https://github.com/apache/calcite/blob/main/site/_data/contributors.yml
[2] https://calcite.apache.org/community/#project-members

Re: [ANNOUNCE] New committer: Zhe Hu

[Francis Chuang]

Congrats, Zhe Hu!

On 28/06/2023 9:04 pm, Stamatis Zampetakis wrote:

Apache Calcite's Project Management Committee (PMC) has invited Zhe Hu to
become a committer, and we are pleased to announce that they have accepted.

Zhe Hu has been contributing to the project for a while now. They
improved the stability of the ElasticSearch adapter, worked on
supporting new java versions, and landed various enhancements around
CONCAT and CONVERT functions.

Zhe Hu, welcome, thank you for your contributions, and we look forward to your
further interactions with the community! If you wish, please feel free to tell
us more about yourself and what you are working on.

As your first commit, please add yourself to the contributors list [1]
and the community page will re-generate [2].

Stamatis (on behalf of the Apache Calcite PMC)

[1] https://github.com/apache/calcite/blob/main/site/_data/contributors.yml
[2] https://calcite.apache.org/community/#project-members

Re: [ANNOUNCE] New committer: Jacky Lau

[Francis Chuang]

Congrats, Jacky!

On 28/06/2023 8:46 pm, Stamatis Zampetakis wrote:

Apache Calcite's Project Management Committee (PMC) has invited Jacky Lau to
become a committer, and we are pleased to announce that they have accepted.

Jacky has started contributing to the project very recently and in a
very short time they landed many notable improvements around ARRAY and
MAP functions with a particular focus on the Spark dialect.

Jacky, welcome, thank you for your contributions, and we look forward to your
further interactions with the community! If you wish, please feel free to tell
us more about yourself and what you are working on.

As your first commit, please add yourself to the contributors list [1]
and the community page will re-generate [2].

Stamatis (on behalf of the Apache Calcite PMC)

[1] https://github.com/apache/calcite/blob/main/site/_data/contributors.yml
[2] https://calcite.apache.org/community/#project-members

Re: [ANNOUNCE] New committer: Oliver Lee

[Francis Chuang]

Congrats, Oliver!

On 13/06/2023 8:44 pm, Stamatis Zampetakis wrote:

Apache Calcite's Project Management Committee (PMC) has invited Oliver
Lee to become a committer, and we are pleased to announce that they
have accepted.

Oliver started working with us around November 2022 and since then
they contributed multiple SQL functions to the Calcite repository
bringing lots of improvements to the BigQuery dialect. They improved
the extensibility of the SQL validator and pushed various fixes in
RelNode serialization to JSON.

Oliver, welcome, thank you for your contributions, and we look forward
to your further interactions with the community! If you wish, please
feel free to tell us more about yourself and what you are working on.

As your first commit, please add yourself to the contributors list [1]
and the community page will re-generate [2].

Stamatis (on behalf of the Apache Calcite PMC)

[1] https://github.com/apache/calcite/blob/main/site/_data/contributors.yml
[2] https://calcite.apache.org/community/#project-members

[jira] [Created] (CALCITE-5758) Initialize connector info map

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-5758:
---

 Summary: Initialize connector info map
 Key: CALCITE-5758
 URL: https://issues.apache.org/jira/browse/CALCITE-5758
 Project: Calcite
  Issue Type: New Feature
  Components: avatica-go
Reporter: Francis Chuang
Assignee: Francis Chuang
 Fix For: avatica-go-5.3.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [ANNOUNCE] New committer: Tanner Clary

[Francis Chuang]

Congrats, Tanner!

On 26/05/2023 7:21 pm, Alessandro Solimando wrote:

Congrats Tanner, welcome aboard!

Best regards,
Alessandro

On Fri, 26 May 2023 at 11:11, Benchao Li  wrote:


Congratulations, Tanner!

Stamatis Zampetakis  于2023年5月26日周五 17:05写道：


Apache Calcite's Project Management Committee (PMC) has invited Tanner
Clary to become a committer, and we are pleased to announce that they
have accepted.

In less than 5 months, Tanner has introduced, enabled, and tested over
30 SQL functions in Calcite. They have been a driving force in
improving the BigQuery dialect and by now an expert in library and
parser changes.

Tanner, welcome, thank you for your contributions, and we look forward
to your further interactions with the community! If you wish, please
feel free to tell us more about yourself and what you are working on.

As your first commit, please add yourself to the contributors list [1]
and the community page will re-generate [2].

Stamatis (on behalf of the Apache Calcite PMC)

[1]
https://github.com/apache/calcite/blob/main/site/_data/contributors.yml

[2] https://calcite.apache.org/community/#project-members




--

Best,
Benchao Li