Re: Reviewing blog post

Hello everyone, I am a little late to the party, but I finally had time to check the blog from Mihai, and it reads extremely well, it goes into enough details to be valuable even for people already knowing Calcite, but at the same time it's great introductory material. I'd be happy to read more

Re: calcite 1.36.0 release procedures

Guillaume, The binary release are always compiled with JDK8, this is a required procedure[1]. For 1.36.0, the JDK version I'm using is: $ java -version java version "1.8.0_371" Java(TM) SE Runtime Environment (build 1.8.0_371-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.371-b11, mixed mode)

calcite 1.36.0 release procedures

Hi all, We recently upgraded to calcite 1.36.0 and it broke our deployment process. We are using java asm to shade (rename packages from the bytecode) since there are multiple dependencies clash when using with Apache Spark. For example, Apache Spark is using a much older

[jira] [Created] (CALCITE-6130) Different physical conventions conversion on new physical node producing

蔡灿材 created CALCITE-6130: Summary: Different physical conventions conversion on new physical node producing Key: CALCITE-6130 URL: https://issues.apache.org/jira/browse/CALCITE-6130 Project: Calcite