Sree Harsha Ramanavarapu created CALCITE-6809:
-
Summary: 8 table join with jdbc connections hangs
Key: CALCITE-6809
URL: https://issues.apache.org/jira/browse/CALCITE-6809
Project: Calcite
Seemed like a relatively simple mechanical change:
https://github.com/apache/calcite-avatica/pull/272
Let me know if anything is inappropriate. Note that due to 1.8 source
compatibility there’s some fairly ugly FQCN references that cannot be avoided.
Chris
From: Julian Hyde
Date: Tuesday, Jan
Why defer 5136? Ignoring deprecation warnings hurt us in the past. We logged
5136 so that it wouldn’t happen again. I think it’s ok to suppress deprecation
warnings that we know are ok, so that we can have the build fail if new
deprecation warnings occur.
> On Jan 28, 2025, at 4:00 AM, Istvan
Istvan Toth created CALCITE-6808:
Summary: Use JDK23 instead of JDK22 in CI test for latest JVM in
Avatica
Key: CALCITE-6808
URL: https://issues.apache.org/jira/browse/CALCITE-6808
Project: Calcite
Thanks to Stamatis and Chris the JDK23 support is in.
According to the 1.26.0 release ticket(CALCITE-6589), there are two more
tasks left:
* A trivial Guava update https://github.com/apache/calcite-avatica/pull/270
* and CALCITE-5136 Avatica build (or CI) must fail if there are deprecation
warning
Istvan Toth created CALCITE-6807:
Summary: Update Guava from 32.1.1-jre to 33.4.0-jre in Avatica
Key: CALCITE-6807
URL: https://issues.apache.org/jira/browse/CALCITE-6807
Project: Calcite
Iss
Stamatis Zampetakis created CALCITE-6806:
Summary: Add CI action to test site remains buildable after changes
Key: CALCITE-6806
URL: https://issues.apache.org/jira/browse/CALCITE-6806
Project:
