[jira] [Created] (CALCITE-4828) Standard Avatica build exception console output

2021-10-04 Thread duan xiong (Jira)
duan xiong created CALCITE-4828: --- Summary: Standard Avatica build exception console output Key: CALCITE-4828 URL: https://issues.apache.org/jira/browse/CALCITE-4828 Project: Calcite Issue

[jira] [Created] (CALCITE-4827) Refactor annotation processor tasks to be used across multiple modules

2021-10-04 Thread Jacques Nadeau (Jira)
Jacques Nadeau created CALCITE-4827: --- Summary: Refactor annotation processor tasks to be used across multiple modules Key: CALCITE-4827 URL: https://issues.apache.org/jira/browse/CALCITE-4827

Re: Avatica dry-run

2021-10-04 Thread Francis Chuang
Hey Julian, I just tested everything in docker and it works if I do the following: Terminal 1: git clone https://github.com/vlsi/asflike-release-environment cd asflike-release-environment ./recreate.sh calcite-avatica ... wait for the mock release environment to finish starting ... Terminal

Re: Avatica dry-run

2021-10-04 Thread Stamatis Zampetakis
I haven't done an avatica release so I don't know if using docker is must but maybe running directly the prepareVote task could work: ./gradlew prepareVote -Prc=0 -Pasf It may complain about missing properties. I have the following on my ~/.gradle/gradle.properties file: useGpgCmd=true

Re: Avatica dry-run

2021-10-04 Thread Julian Hyde
I'm still running into this 'Connection refused' error. It's a show-stopper. I cannot make a release candidate unless this problem is solved. On Mon, Oct 4, 2021 at 10:58 AM Julian Hyde wrote: > > This is the command I used: > > docker-compose run -v ~/.gnupg:/.gnupg dry-run > > I'm running

Re: Avatica dry-run

2021-10-04 Thread Julian Hyde
This is the command I used: docker-compose run -v ~/.gnupg:/.gnupg dry-run I'm running Docker 18.06.1-ce on Ubuntu 20.04.3 LTS. By the way, I was thinking of creating a "stage" branch in the Avatica git repo. We no longer use a branch per release (which is fine) but this means that the commit

Re: Avatica dry-run

2021-10-04 Thread Vladimir Sitnikov
I'm not sure which steps are you following, however, the same sequence seems to work fine: Commands: https://github.com/vlsi/vlsi-release-plugins/blob/83c85c5faa4c7cd1fe0173b75c1cba5e60c3f209/.github/workflows/release-test.yml#L33-L60 Logs:

[jira] [Created] (CALCITE-4826) Fix Intellij annotation processing failure post CALCITE-4787

2021-10-04 Thread Jacques Nadeau (Jira)
Jacques Nadeau created CALCITE-4826: --- Summary: Fix Intellij annotation processing failure post CALCITE-4787 Key: CALCITE-4826 URL: https://issues.apache.org/jira/browse/CALCITE-4826 Project:

Review request: CALCITE-4818 (AggregateExpandDistinctAggregatesRule must infer correct data type for top aggregate calls)

2021-10-04 Thread Taras Ledkov
Hi, Please review the patch for the issue CALCITE-4818 [1], see PR#2560 [2]. Looks like the rule 'AggregateExpandDistinctAggregatesRule' contains another bug with inferring result type of the top aggregate calls. e.g. If the type system expand sum type like postgress: SUM(TINYINT | SMALLINT

Avatica dry-run

2021-10-04 Thread Julian Hyde
As release manager for the upcoming Avatica 1.19, I just tried to use the docker-based dry-run. I got the following failure: Build calcite-avatica FAILURE reason: Execution failed for task ':initializeNexusStagingRepository': java.io.UncheckedIOException: java.net.ConnectException:

[jira] [Created] (CALCITE-4825) Update enumerables rules to use immutables instead of ImmutableBeans.EMPTY

2021-10-04 Thread Jacques Nadeau (Jira)
Jacques Nadeau created CALCITE-4825: --- Summary: Update enumerables rules to use immutables instead of ImmutableBeans.EMPTY Key: CALCITE-4825 URL: https://issues.apache.org/jira/browse/CALCITE-4825

[jira] [Created] (CALCITE-4824) ServerUnParserTest#testCreateTableVirtualColumn fails

2021-10-04 Thread Vladimir Sitnikov (Jira)
Vladimir Sitnikov created CALCITE-4824: -- Summary: ServerUnParserTest#testCreateTableVirtualColumn fails Key: CALCITE-4824 URL: https://issues.apache.org/jira/browse/CALCITE-4824 Project: Calcite

Re: [DISCUSS] Move CalciteAssert and similar "test framework" classes to its own testlib module

2021-10-04 Thread Vladimir Sitnikov
As suggested above, I've prepared a PR that moves CalciteAssert, Matchers, and a couple of test schemata to the new :testkit module. calcite-*-tests.jar will no longer be published. PR: https://github.com/apache/calcite/pull/2558 The tests pass, and the change unlocks migration to Gradle 7.2

[jira] [Created] (CALCITE-4823) JEP 411: AccessControlException, AccessController in java.security has been deprecated and marked for removal

2021-10-04 Thread Vladimir Sitnikov (Jira)
Vladimir Sitnikov created CALCITE-4823: -- Summary: JEP 411: AccessControlException, AccessController in java.security has been deprecated and marked for removal Key: CALCITE-4823 URL: