Hi all,
I have created a build for Apache Calcite 1.31.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.31.0-rc0/site/_docs/history.md
The commit to be voted upon:
It should be all good now.
My problem was that I use different accounts for github and gitbox.
For some reason the gradle release plugin was using github credentials (
asfGitSourceUsername property) and not nexus ones (asfNexusUsername) from
~/.gradle/gradle.properties. Maybe because of the
Thanks, Julian. I did include GITBOX in the prepare vote command.
$ gradle prepareVote -Prc=0 -Pasf -Pasf.git.pushRepositoryProvider=GITBOX
On Fri, Jul 22, 2022 at 1:31 PM Julian Hyde wrote:
> Andrei, Are you perhaps running into
> https://issues.apache.org/jira/browse/CALCITE-4856 ?
>
> On
It would certainly be possible to write a planner rule that converts a Calc to
a sequence of Project and an optional Filter.
However, it might not yield optimal performance. Consider this query:
SELECT a AS x1,
a + b AS x2,
a + b + c AS x3,
a + b + c + d AS x4,
a + b + c + d +
Andrei, Are you perhaps running into
https://issues.apache.org/jira/browse/CALCITE-4856 ?
On Fri, Jul 22, 2022 at 7:36 AM Andrei Sereda wrote:
>
> Quick update.
>
> I've addressed all comments in the release notes PR.
>
> While tagging RC0, I've run into small issue with apache gitbox
>
I don’t know of any such facility. I suppose someone could do for AST trees
what RelJson and RelWriterTest do for RelNode trees.
Can you please log a Jira case for this? It’s good to have a placeholder in
case someone feels like picking it up in future.
Julian
[1]
Quick update.
I've addressed all comments in the release notes PR.
While tagging RC0, I've run into small issue with apache gitbox
authorization (see below) but should be able to solve them (I've released
1.25 in the past without problems with the new gradle process)
> Task :pushRcTag
Pushing
