[VOTE] Release apache-calcite-1.23.0 (release candidate 0)

2020-05-11 Thread Haisheng Yuan
Hi all, I have created a build for Apache Calcite 1.23.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.23.0-rc0/site/_docs/history.md The commit to be voted upon:

Re: [DISCUSS] Towards Calcite 1.23.0

2020-05-11 Thread Haisheng Yuan
Fixed. I had to send keys to keyserver in the command line. On 2020/05/12 02:49:49, Haisheng Yuan wrote: > Hi, > I am very close to roll out RC0. But met the following error: > Build calcite FAILURE reason: > Execution failed for task ':closeRepository': >

Re: [DISCUSS] Towards Calcite 1.23.0

2020-05-11 Thread Haisheng Yuan
Hi, I am very close to roll out RC0. But met the following error: Build calcite FAILURE reason: Execution failed for task ':closeRepository': io.codearte.gradle.nexus.exception.UnexpectedRepositoryState: Wrong 'orgapachecalcite-1084' repository state 'open' after transition (expected

[jira] [Created] (CALCITE-3992) Beam ZetaSQL supports pure SQL user-defined aggregation functions

2020-05-11 Thread Rui Wang (Jira)
Rui Wang created CALCITE-3992: - Summary: Beam ZetaSQL supports pure SQL user-defined aggregation functions Key: CALCITE-3992 URL: https://issues.apache.org/jira/browse/CALCITE-3992 Project: Calcite

[jira] [Created] (CALCITE-3991) the required boolean should always be provided in RelSet.getOrCreateSubset()

2020-05-11 Thread Botong Huang (Jira)
Botong Huang created CALCITE-3991: - Summary: the required boolean should always be provided in RelSet.getOrCreateSubset() Key: CALCITE-3991 URL: https://issues.apache.org/jira/browse/CALCITE-3991

[jira] [Created] (CALCITE-3990) Use a more efficient algorithm for cost propagation in Volcano planner

2020-05-11 Thread James Kim (Jira)
James Kim created CALCITE-3990: -- Summary: Use a more efficient algorithm for cost propagation in Volcano planner Key: CALCITE-3990 URL: https://issues.apache.org/jira/browse/CALCITE-3990 Project:

[jira] [Created] (CALCITE-3989) Release Calcite 1.23.0

2020-05-11 Thread Haisheng Yuan (Jira)
Haisheng Yuan created CALCITE-3989: -- Summary: Release Calcite 1.23.0 Key: CALCITE-3989 URL: https://issues.apache.org/jira/browse/CALCITE-3989 Project: Calcite Issue Type: Task

Calcite-Master - Build # 1753 - Still Failing

2020-05-11 Thread Apache Jenkins Server
The Apache Jenkins build system has built Calcite-Master (build #1753) Status: Still Failing Check console output at https://builds.apache.org/job/Calcite-Master/1753/ to view the results.

Calcite-Master - Build # 1752 - Failure

2020-05-11 Thread Apache Jenkins Server
The Apache Jenkins build system has built Calcite-Master (build #1752) Status: Failure Check console output at https://builds.apache.org/job/Calcite-Master/1752/ to view the results.

Re: [DISCUSS] Towards Cascades Optimizer

2020-05-11 Thread Julian Hyde
If there’s a way for all of these efforts to be committed to master, disabled by default, but such that they can be enabled by setting a flag, then we can at least avoid merge conflicts. I hope that this “trunk-based development” approach is technically feasible. If the rule and metadata APIs

Re: [DISCUSS] Towards Calcite 1.23.0

2020-05-11 Thread Haisheng Yuan
Quick question, does the RC0 need to have fully updated history.md? On 2020/05/11 13:51:53, Haisheng Yuan wrote: > Oops, thanks for reminding. lol > > On 2020/05/11 09:41:33, Stamatis Zampetakis wrote: > > Previously you mentioned: > > ~/vlsi-release-plugins ❯❯❯ ./gradlew prepareVote -Prc=0

Re: [DISCUSS] Towards Cascades Optimizer

2020-05-11 Thread Roman Kondakov
Hi Jinpeng, Apache Calcite community has entered into the interesting situation: we have several concurrent efforts of building the new Cascades style optimizers. I can see at least three activities (correct me if I'm wrong): 1. Haisheng's gradual rebuilding of VolcanoPlanner [1] 2. Jinpeng's

Re: [DISCUSS] Towards Calcite 1.23.0

2020-05-11 Thread Haisheng Yuan
Oops, thanks for reminding. lol On 2020/05/11 09:41:33, Stamatis Zampetakis wrote: > Previously you mentioned: > ~/vlsi-release-plugins ❯❯❯ ./gradlew prepareVote -Prc=0 > > Just to be sure for releasing Calcite you should execute ./gradlew > prepareVote -Prc=0 in calcite directory (not in

[jira] [Created] (CALCITE-3988) Intersect in RelMdRowCount doesn't take into account 'intersect all'

2020-05-11 Thread xzh_dz (Jira)
xzh_dz created CALCITE-3988: --- Summary: Intersect in RelMdRowCount doesn't take into account 'intersect all' Key: CALCITE-3988 URL: https://issues.apache.org/jira/browse/CALCITE-3988 Project: Calcite

Re: [DISCUSS] Towards Calcite 1.23.0

2020-05-11 Thread Stamatis Zampetakis
Previously you mentioned: ~/vlsi-release-plugins ❯❯❯ ./gradlew prepareVote -Prc=0 Just to be sure for releasing Calcite you should execute ./gradlew prepareVote -Prc=0 in calcite directory (not in vlsi-release-plugins). On Mon, May 11, 2020 at 11:03 AM Haisheng Yuan wrote: > Hi Stamatis, > > I

Re: [DISCUSS] Towards Calcite 1.23.0

2020-05-11 Thread Haisheng Yuan
Hi Stamatis, I tried to add all the info to the property file, still no luck: signing.gnupg.keyName=3CD22ABAC50DDCEF asfCommitterId=hyuan ghTestGitSourceUsername=test ghTestGitSourcePassword=test ghTestNexusUsername=test ghTestNexusPassword=test asfGitSourceUsername=test

Re: [DISCUSS] Towards Calcite 1.23.0

2020-05-11 Thread Stamatis Zampetakis
Hi Haisheng, You might be missing some gradle.properties especially those required to identify your PGP key. Have a look in the discussion in [1]. Among other info it contains also the complete list of properties. Best, Stamatis [1]

Re: [DISCUSS] Towards Cascades Optimizer

2020-05-11 Thread Jinpeng Wu
Hi, Roman. Thanks to Julian's tips, I added a CoreCascadeQuidemTest to the code. It runs iq files that CoreQuidemTest would runs and uses CascadePlanner instead of VolcanoPlanner to generate physical plans. Currently all tests have passed. There are some plan changes but they are actually

Re: [DISCUSS] Towards Calcite 1.23.0

2020-05-11 Thread Haisheng Yuan
Hi, I saw this error during the dry-run: ~/vlsi-release-plugins ❯❯❯ ./gradlew prepareVote -Prc=0 > Task :plugins:crlf-plugin:signCrlfPluginMarkerMavenPublication FAILED > Task > :plugins:checksum-dependency-plugin:signChecksum-dependencyPluginMarkerMavenPublication > FAILED > Task