Marieke Gueye created CALCITE-5052:
--
Summary: Calcite testkit issue loading resources from jar in
DiffRepository (bazel)
Key: CALCITE-5052
URL: https://issues.apache.org/jira/browse/CALCITE-5052
Ubuntu 20.04.4 LTS, jdk1.8.0_261, Gradle wrapper, Gradle 6.8.3
* Checked signatures and checksums OK
* Went over release note OK
* Built from git tag and run tests (./gradlew clean build) OK
* Built from source artifacts and run unit tests + slow tests OK
* Checked diff between repo and
That sounds very reasonable to me
I don't know the Calcite codebase as well as other folks -- and certainly
not nearly as well as you
Where would be the place to put such a thing/the overall approach?
On Fri, Mar 18, 2022 at 1:53 PM Julian Hyde wrote:
> I think you’re proposing making the
+1
Checked checksums and signatures, compared with git repo at same sha, checked
LICENSE, NOTICE, README, howto.md, release notes, compiled and ran tests on
Ubuntu 20.04.4 LTS Linux 5.4.0-104-generic x86_64 using JDK 11 and Gradle 7.2
(noting that the recommended Gradle version is 7.3), ran
Zachary Gramana created CALCITE-5051:
Summary: UNION query plan prevents projection push down
Key: CALCITE-5051
URL: https://issues.apache.org/jira/browse/CALCITE-5051
Project: Calcite
I think you’re proposing making the JSON_ functions smarter at runtime. My
general philosophy is to have the smarts at prepare time and make the runtime
operators dumb. I think that philosophy can be applied here. Some extra logic
would kick in when preparing a query that has JSON_ functions,
We implemented support for `SET SCHEMA` by subclassing `ServerDdlExecutor`, and
calling (in our case) `AvaticaConnection.setSchema(schema)` does indeed work.
However, we've also encountered some JDBC-based applications that will set the
explicitly set an incorrect default schema via the
Sorry to beat a dead horse here, but I'm one of those weirdos that gets a
lot of use out of Calcite's JSON operators.
Calcite's JSON implementation is broken for queries that have more than one
depth of JSON object/array calls.
The reason is because the operator calls "jsonize()", which parses
+1 (binding)
Checked hash and compiled and ran tests. Thanks for being RM!
--
Michael Mior
mm...@apache.org
Le mar. 15 mars 2022 à 23:36, Fan Liya a écrit :
> Hi all,
>
> I have created a build for Apache Calcite 1.30.0, release
> candidate 3.
>
> Thanks to everyone who has contributed to
