Re: [ANNOUNCE] Master branch renamed to main

Quick update. I just did a dry-run release for Avatica and it built fine without needing to set the branch in vlsi-release-plugin's configuration. The plugin only pushes tags to git and I don't think it ever commits any files, so I don't think it needs to know about us renaming our default

[jira] [Created] (CALCITE-5117) Optimize the EXISTS sub-query by Metadata RowCount

xiong duan created CALCITE-5117: --- Summary: Optimize the EXISTS sub-query by Metadata RowCount Key: CALCITE-5117 URL: https://issues.apache.org/jira/browse/CALCITE-5117 Project: Calcite Issue

[DISCUSS] Towards Calcite-Avatica 1.21.0

Hey everyone, The last release for Avatica (1.20.0) was in December last year, so it's about time to release Avatica 1.21.0. This release should be a pretty straight-forward and routine release as we only have a handful of commits to Avatica since the last release. Here's a list of issues

[jira] [Created] (CALCITE-5116) Unable to build Avatica release with Gradle 7.4.2

Francis Chuang created CALCITE-5116: --- Summary: Unable to build Avatica release with Gradle 7.4.2 Key: CALCITE-5116 URL: https://issues.apache.org/jira/browse/CALCITE-5116 Project: Calcite

Re: [ANNOUNCE] Master branch renamed to main

Not sure how the stage-vote-release-plugin works internally, but I think the branch is not set in calcite and calcite-avatica originally, so perhaps it's smart enough to use the name of the current branch instead of defaulting to master. On 27/04/2022 9:03 am, Michael Mior wrote: One

Jenkins build is back to normal : Calcite » Calcite-snapshots #134

See

Build failed in Jenkins: Calcite » Calcite-snapshots #133

See Changes: [Francis Chuang] Revert "Remove branch setting in release configuration" -- Started by GitHub push by F21 Started by GitHub push by F21

Re: [ANNOUNCE] Master branch renamed to main

One outstanding issue is that I was unable to set the branch to main for stage-vote-release-plugin. I believe it may default to "master", so I'm not sure if we'll run into issues on the next release. -- Michael Mior mm...@apache.org Le mar. 26 avr. 2022 à 16:30, Julian Hyde a écrit : > Thanks,

Re: [ANNOUNCE] Master branch renamed to main

Thanks, Michael. It all looks good from my end. I had opened a pull request yesterday (when the branch was named 'master') and it merged smoothly today (after the rename). Julian On Tue, Apr 26, 2022 at 7:54 AM Michael Mior wrote: > > The master branch has now been renamed to main. If you have

[ANNOUNCE] Master branch renamed to main

The master branch has now been renamed to main. If you have an existing checkout, please follow the steps below (thanks to Francis!) to ensure your local master branch is also correctly renamed. Note that if you do not have any local changes, you can also simply clone a new copy of the repository

[jira] [Created] (CALCITE-5115) upgrade jackson due to CVE-2020-36518

Florian Brams created CALCITE-5115: -- Summary: upgrade jackson due to CVE-2020-36518 Key: CALCITE-5115 URL: https://issues.apache.org/jira/browse/CALCITE-5115 Project: Calcite Issue Type:

[jira] [Created] (CALCITE-5114) SqlParseException for Spark's "corr" function

Laurens Versluis created CALCITE-5114: - Summary: SqlParseException for Spark's "corr" function Key: CALCITE-5114 URL: https://issues.apache.org/jira/browse/CALCITE-5114 Project: Calcite

[jira] [Created] (CALCITE-5113) function week(date 'xxx') return an error number

itxiangkui created CALCITE-5113: --- Summary: function week(date 'xxx') return an error number Key: CALCITE-5113 URL: https://issues.apache.org/jira/browse/CALCITE-5113 Project: Calcite Issue