Re: [ANNOUNCE] Apache Calcite 1.36.0 released

2023-11-10 Thread Michael Behrendt 
Could the value prop be that it provides ephemeral k8s clusters? Incl openshift

‘Run’ as the wideest command, supporting everythinh

Incl cli, sdk and also web usage

Also many regions at the same time

From: Benchao Li 
Date: Friday, 10. November 2023 at 15:31
To: dev@calcite.apache.org , Apache Announce List 

Subject: [EXTERNAL] [ANNOUNCE] Apache Calcite 1.36.0 released
The Apache Calcite team is pleased to announce the release of Apache
Calcite 1.36.0.

Calcite is a dynamic data management framework. Its cost-based
optimizer converts queries, represented in relational algebra, into
executable plans. Calcite supports many front-end languages and
back-end data engines, and includes an SQL parser and, as a
sub-project, the Avatica JDBC driver.

This release comes three months after 1.35.0. It includes more than
125 resolved issues, comprising of a few new features as well as
general improvements and bug-fixes. It includes more than 30 new
functions, various improvements hardening TABLESAMPLE, and also the
integration of SQL Logic Test suite.

You can start using it in Maven by simply updating your dependency to:


org.apache.calcite
calcite-core
1.36.0


If you'd like to download the source release, you can find it here:

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

You can read more about the release (including release notes) here:

https://calcite.apache.org/news/2023/11/10/release-1.36.0/

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/

Thanks to everyone involved!

Benchao Li, on behalf of the Apache Calcite Team

--

Best,
Benchao Li

[jira] [Created] (CALCITE-6105) Documentation does not specify the behavior of SPLIT function for empty string arguments

2023-11-10 Thread Mihai Budiu (Jira) 
Mihai Budiu created CALCITE-6105:


 Summary: Documentation does not specify the behavior of SPLIT 
function for empty string arguments
 Key: CALCITE-6105
 URL: https://issues.apache.org/jira/browse/CALCITE-6105
 Project: Calcite
  Issue Type: Bug
  Components: core
Affects Versions: 1.36.0
Reporter: Mihai Budiu


Various string libraries choose different behaviors for SPLIT when the first or 
the second arguments are empty strings.



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

[jira] [Created] (CALCITE-6104) Aggregate function that references outer column should be evaluated in outer query

2023-11-10 Thread Julian Hyde (Jira) 
Julian Hyde created CALCITE-6104:


 Summary: Aggregate function that references outer column should be 
evaluated in outer query
 Key: CALCITE-6104
 URL: https://issues.apache.org/jira/browse/CALCITE-6104
 Project: Calcite
  Issue Type: Improvement
Reporter: Julian Hyde


Aggregate function that references outer column should be evaluated in outer 
query. For example,

{code}
WITH
  aa AS (SELECT 1 AS a UNION ALL SELECT 2 UNION ALL SELECT 3),
  xx AS (SELECT 10 AS x UNION ALL SELECT 20 UNION ALL SELECT 30)
SELECT (SELECT sum(a) FROM xx LIMIT 1) AS sa FROM aa;

# Should return
sa
--
6

# Currently returns
sa
--
3
6
9
{code}

Because {{sum(a)}} references a column from {{aa}} (and no columns from 
{{{}xx{}}}), it should be (per the SQL standard) evaluated in the context of 
the outer query.

Postgres, MySQL and DuckDB have behavior consistent with the standard. Calcite 
and BigQuery do not.

A [blog 
post|https://buttondown.email/jaffray/archive/sql-scoping-is-surprisingly-subtle-and-semantic/]
 describes in more detail.
 



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

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

2023-11-10 Thread Apache Jenkins Server 
See

Re: all zeros in the result set for float/double, Avatica-Go

2023-11-10 Thread Julian Hyde 
Please log a bug.

> On Nov 10, 2023, at 7:54 AM, Egor Ryashin  wrote:
> 
> Hi all,
> 
> FYI, having all zeros in Go client result set with Calcite 1.35 update in 
> Apache Druid. It worked with the older version. From what I see in the 
> debugger TypedValue.NumberValue = 0 but DoubleValue = 1. Not sure where's the 
> bug exactly - Druid/Avatica.
> 
> This is how it can be reproduced:
> package main
> 
> import (
>   "database/sql"
>   "fmt"
> 
>   _ "github.com/apache/calcite-avatica-go/v5"
> )
> 
> func main() {
> 
>   jdbcUrl := "https://localhost/druid/v2/sql/avatica-protobuf;
> 
>   db, err := sql.Open("avatica", jdbcUrl)
>   if err != nil {
> panic(err)
>   }
>   defer db.Close()
> 
>   sql4 := `
>   SELECT
>   cast(1.0 as double) m3
>   `
> 
>   rows, err := db.Query(sql4)
>   if err != nil {
> panic(err)
>   }
>   defer rows.Close()
> 
>   var m1 float32
> 
>   for rows.Next() {
> err := rows.Scan()
> if err != nil {
>   panic(err)
> }
> fmt.Println(m1)
>   }
> }
> What I see in the debugger right now:
>

Re: [DISCUSS] Towards Calcite 1.36.0

2023-11-10 Thread Benchao Li 
Hi all, main code freeze is over and commits can resume. Thank you all
who involved in the releasing of 1.36.0.

Benchao Li  于2023年11月10日周五 19:06写道：

>
> 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

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

2023-11-10 Thread Apache Jenkins Server 
See 


Changes:

[Benchao Li] Prepare for next development iteration


--
[...truncated 397.30 KB...]
> Task :elasticsearch:test
2023-11-10 14:01:22,590 [elasticsearch[fake-elastic][scheduler][T#1]] WARN  
- [gc][1] overhead, spent [2.5s] collecting in the last [3.1s]

> Task :testkit:test

FixtureTest > testSqlToRelFixtureNeedsDiffRepos() STANDARD_ERROR
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
  0.8sec,1 completed,   0 failed,   0 skipped, 
org.apache.calcite.TestKtTest
  0.9sec,5 completed,   0 failed,   0 skipped, 
org.apache.calcite.util.TestUtilTest
  2.8sec, org.apache.calcite.test.FixtureTest > 
testValidatorFixture()
  5.8sec, org.apache.calcite.test.FixtureTest > 
testSqlToRelFixture()
  6.1sec, org.apache.calcite.test.FixtureTest > 
testRuleFixtureNeedsDiffRepos()
  7.2sec, org.apache.calcite.test.FixtureTest > 
testMetadata()
  7.6sec, org.apache.calcite.test.FixtureTest > 
testRuleFixture()
 10.4sec, org.apache.calcite.test.FixtureTest > 
testOperatorFixture()
 10.7sec,9 completed,   0 failed,   0 skipped, 
org.apache.calcite.test.FixtureTest
 17.8sec,   15 completed,   0 failed,   0 skipped, Gradle Test Run 
:testkit:test

> Task :testkit:check
> Task :testkit:build
> Task :testkit:generateMetadataFileForTestkitPublication SKIPPED

> Task :server:test
  6.1sec, org.apache.calcite.test.ServerQuidemTest 
> test(String)[6], [6] sql/materialized_view.iq
 46.2sec,6 completed,   0 failed,   0 skipped, 
org.apache.calcite.test.ServerQuidemTest > test(String)
 46.8sec,6 completed,   0 failed,   0 skipped, 
org.apache.calcite.test.ServerQuidemTest
FAILURE  57.6sec, 1039 completed,   2 failed, 
  8 skipped, Gradle Test Run :server:test

1039 tests completed, 2 failed, 8 skipped

> Task :server:test FAILED

> Task :piglet:test
 25.0sec, org.apache.calcite.test.PigRelExTest > 
testNotEqual()
 24.9sec, org.apache.calcite.test.PigRelExTest > 
testAdd()
 24.9sec, org.apache.calcite.test.PigRelExTest > 
testMod()
 25.0sec, org.apache.calcite.test.PigRelExTest > 
testIsNotNull()
 25.2sec, org.apache.calcite.test.PigRelExTest > 
testLessThan()
 25.4sec, org.apache.calcite.test.PigRelExTest > 
testNegation()
 25.5sec, org.apache.calcite.test.PigRelExTest > 
testNot()
 25.6sec, org.apache.calcite.test.PigRelOpTest > 
testLoadWithSchema()
 25.6sec, org.apache.calcite.test.PigRelExTest > 
testAnd()
  7.8sec, org.apache.calcite.test.PigRelOpTest > 
testLoadWithoutSchema()
  2.1sec, org.apache.calcite.test.PigletTest > 
testDump()
  5.0sec, org.apache.calcite.test.PigRelOpTest > 
testFlattenStrSplit()
  2.2sec, org.apache.calcite.test.PigRelExTest > 
testGreaterThanEqual()
  2.1sec, org.apache.calcite.test.PigRelExTest > 
testProjection()
 27.2sec, org.apache.calcite.test.PigScriptTest > 
testReadScript()
 27.7sec,1 completed,   0 failed,   0 skipped, 
org.apache.calcite.test.PigScriptTest
  4.9sec, org.apache.calcite.test.PigletTest > 
testFilterExample()
WARNING  28.0sec,   19 completed,   0 failed,   1 
skipped, org.apache.calcite.test.PigletTest
 27.6sec, org.apache.calcite.test.PigRelOpTest > 
testUdf()
  2.4sec, org.apache.calcite.test.PigRelOpTest > 
testSample()
 28.0sec, org.apache.calcite.test.PigRelOpTest > 
testLimit()
 28.4sec, org.apache.calcite.test.PigRelOpTest > 
testUnionDifferentSchemas1()
  5.9sec, org.apache.calcite.test.PigRelOpTest > 
testMultipleStores()
 28.6sec, org.apache.calcite.test.PigRelOpTest >

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

2023-11-10 Thread Apache Jenkins Server 
See

[ANNOUNCE] Apache Calcite 1.36.0 released

2023-11-10 Thread Benchao Li 
The Apache Calcite team is pleased to announce the release of Apache
Calcite 1.36.0.

Calcite is a dynamic data management framework. Its cost-based
optimizer converts queries, represented in relational algebra, into
executable plans. Calcite supports many front-end languages and
back-end data engines, and includes an SQL parser and, as a
sub-project, the Avatica JDBC driver.

This release comes three months after 1.35.0. It includes more than
125 resolved issues, comprising of a few new features as well as
general improvements and bug-fixes. It includes more than 30 new
functions, various improvements hardening TABLESAMPLE, and also the
integration of SQL Logic Test suite.

You can start using it in Maven by simply updating your dependency to:


org.apache.calcite
calcite-core
1.36.0


If you'd like to download the source release, you can find it here:

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

You can read more about the release (including release notes) here:

https://calcite.apache.org/news/2023/11/10/release-1.36.0/

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/

Thanks to everyone involved!

Benchao Li, on behalf of the Apache Calcite Team

-- 

Best,
Benchao Li

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

2023-11-10 Thread Apache Jenkins Server 
See 


Changes:


--
[...truncated 9.03 KB...]
> Task :buildSrc:fmpp:autostyleKotlinCheck
> Task :buildSrc:fmpp:autostyleKotlinGradleCheck
> Task :buildSrc:fmpp:autostyleCheck
> Task :buildSrc:fmpp:processTestResources NO-SOURCE
> Task :buildSrc:javacc:autostyleKotlinCheck
> Task :buildSrc:javacc:autostyleKotlinGradleCheck
> Task :buildSrc:javacc:autostyleCheck
> Task :buildSrc:javacc:processTestResources NO-SOURCE

> Task :buildSrc:javacc:compileKotlin
w: 
:
 (66, 13): 'setter for main: String?' is deprecated. Deprecated in Java

> Task :buildSrc:javacc:compileJava NO-SOURCE
> Task :buildSrc:javacc:classes
> Task :buildSrc:javacc:inspectClassesForKotlinIC
> Task :buildSrc:fmpp:compileKotlin
> Task :buildSrc:fmpp:compileJava NO-SOURCE
> Task :buildSrc:fmpp:classes
> Task :buildSrc:buildext:compileKotlin
> Task :buildSrc:buildext:compileJava NO-SOURCE
> Task :buildSrc:buildext:classes
> Task :buildSrc:buildext:inspectClassesForKotlinIC
> Task :buildSrc:fmpp:inspectClassesForKotlinIC
> Task :buildSrc:javacc:jar
> Task :buildSrc:javacc:assemble
> Task :buildSrc:javacc:compileTestKotlin NO-SOURCE
> Task :buildSrc:javacc:compileTestJava NO-SOURCE
> Task :buildSrc:buildext:jar
> Task :buildSrc:buildext:assemble
> Task :buildSrc:buildext:compileTestKotlin NO-SOURCE
> Task :buildSrc:fmpp:jar
> Task :buildSrc:buildext:compileTestJava NO-SOURCE
> Task :buildSrc:fmpp:assemble
> Task :buildSrc:test NO-SOURCE
> Task :buildSrc:check
> Task :buildSrc:build
> Task :buildSrc:javacc:pluginUnderTestMetadata
> Task :buildSrc:javacc:testClasses UP-TO-DATE
> Task :buildSrc:fmpp:compileTestKotlin NO-SOURCE
> Task :buildSrc:buildext:pluginUnderTestMetadata
> Task :buildSrc:buildext:testClasses UP-TO-DATE
> Task :buildSrc:javacc:test NO-SOURCE
> Task :buildSrc:buildext:test NO-SOURCE
> Task :buildSrc:fmpp:compileTestJava NO-SOURCE
> Task :buildSrc:fmpp:pluginUnderTestMetadata
> Task :buildSrc:fmpp:testClasses UP-TO-DATE
> Task :buildSrc:fmpp:test NO-SOURCE
> Task :buildSrc:buildext:validatePlugins
> Task :buildSrc:buildext:check
> Task :buildSrc:buildext:build
> Task :buildSrc:fmpp:validatePlugins
> Task :buildSrc:fmpp:check
> Task :buildSrc:fmpp:build
> Task :buildSrc:javacc:validatePlugins
> Task :buildSrc:javacc:check
> Task :buildSrc:javacc:build

> Configure project :
Building Apache Calcite 1.36.0-SNAPSHOT

Build calcite FAILURE reason:  
  
Caused by: Please correct the following before proceeding with the release:
1) Project property 'asfNexusUsername' is not specified
2) Project property 'asfNexusPassword' is not specified

at 
com.github.vlsi.gradle.release.StageVoteReleasePlugin.runValidations(StageVoteReleasePlugin.kt:422)
at 
com.github.vlsi.gradle.release.StageVoteReleasePlugin.access$runValidations(StageVoteReleasePlugin.kt:63)
at 
com.github.vlsi.gradle.release.StageVoteReleasePlugin$configureRoot$13.execute(StageVoteReleasePlugin.kt:329)
at 
com.github.vlsi.gradle.release.StageVoteReleasePlugin$configureRoot$13.execute(StageVoteReleasePlugin.kt:63)
at 
org.gradle.configuration.internal.DefaultListenerBuildOperationDecorator$BuildOperationEmittingInvocationHandler$1.lambda$run$0(DefaultListenerBuildOperationDecorator.java:255)
at 
org.gradle.configuration.internal.DefaultUserCodeApplicationContext$CurrentApplication.reapply(DefaultUserCodeApplicationContext.java:98)
at 
org.gradle.configuration.internal.DefaultListenerBuildOperationDecorator$BuildOperationEmittingInvocationHandler$1.run(DefaultListenerBuildOperationDecorator.java:253)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47)
at 
org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:68)
at

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

2023-11-10 Thread Apache Jenkins Server 
See

Re: [DISCUSS] Towards Calcite 1.36.0

2023-11-10 Thread Benchao Li 
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

[jira] [Created] (CALCITE-6103) Use eclipse-temurin to build and publish javadocs for the website

2023-11-10 Thread 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

2023-11-10 Thread 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/213c13776651f83f95dceb9645a15e940ec6dce1

Re: [DISCUSS] Towards Calcite 1.36.0

2023-11-10 Thread Benchao Li 
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

Re: [DISCUSS] Towards Calcite 1.36.0

2023-11-10 Thread 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]

Re: [DISCUSS] Towards Calcite 1.36.0

2023-11-10 Thread Benchao Li 
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
>

[jira] [Created] (CALCITE-6102) SqlWriter in SqlInsert's unparse start a list but does not end it

2023-11-10 Thread Mingcan Wang (Jira) 
Mingcan Wang created CALCITE-6102:
-

 Summary: SqlWriter in SqlInsert's unparse start a list but does 
not end it
 Key: CALCITE-6102
 URL: https://issues.apache.org/jira/browse/CALCITE-6102
 Project: Calcite
  Issue Type: Bug
Reporter: Mingcan Wang






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

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

2023-11-10 Thread Benchao Li 
Thanks to everyone who has tested the release candidate and given
their comments and votes.

The tally is as follows.

5 binding +1s:
- Benchao Li
- Julian Hyde
- Francis Chuang
- Ruben Quesada Lopez
- Stamatis Zampetakis

3 non-binding +1s:
- Lei Shen
- Bertil Chapuis
- Ran Tao

No 0s or -1s.

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

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

There was some feedback during voting. I shall open a separate
thread to discuss.

-- 

Best,
Benchao Li