Main Force Push

Sorry for merging a PR without squashing the commits today, I have fixed this to keep the main branch clean(used `--force-with-lease`. This is a better practice learned from previous similar force-push accidents). There are no commits on top so no hashes should be disrupted or anything like that,

Re: calcite 1.36.0 release procedures

If I build 1.36.0 and 1.35.0 with the same java version/build javap can read the classfiles. Since the release process is manual it's really hard to know what causes the problem. My solution is to build and release each Calcite version myself and host it on our own S3 repository. On Mon, Dec 18,

Case-sensitive parser configuration for quoted identifiers

Hello Team, We are attempting to use Calcite as a dialect specific SQL string generator / optimizer for SQL queries systematically generated by Legend data management platform (https://github.com/finos/legend). In this context, I am trying to find if there exists a Calcite parser

Re: calcite 1.36.0 release procedures

Hello, My project also recently upgraded to Calcite 1.36, and we are facing the exact same issue when trying to shade with ASM. @Guillame , I can see that https://gitlab.ow2.org/asm/asm/-/issues/318008 has been closed, but I can't really understand why, since the explanation mentions

Re: Case-sensitive parser configuration for quoted identifiers

Yes, Calcite can do this. In CalciteConnectionProperty [1] there are separate properties QUOTED_CASING and UNQUOTED_CASING. Hopefully you can figure out how to set them. Julian [1] https://calcite.apache.org/javadocAggregate/org/apache/calcite/config/CalciteConnectionProperty.html > On Dec

[jira] [Created] (CALCITE-6169) EnumUtils.convert does not implement the correct SQL cast semantics

Mihai Budiu created CALCITE-6169: Summary: EnumUtils.convert does not implement the correct SQL cast semantics Key: CALCITE-6169 URL: https://issues.apache.org/jira/browse/CALCITE-6169 Project:

warnings in Calcite

Does calcite have any facilities for reporting warnings to users? Thank you, Mihai

[jira] [Created] (CALCITE-6168) RexExecutor can throw during compilation

Mihai Budiu created CALCITE-6168: Summary: RexExecutor can throw during compilation Key: CALCITE-6168 URL: https://issues.apache.org/jira/browse/CALCITE-6168 Project: Calcite Issue Type: Bug

Re: warnings in Calcite

I don’t think so. One place to surface warnings would be via java.sql.Statement.getWarnings() but Avatica’s default implementation of that method returns null. What are some scenarios where you think Calcite should give a warning? Julian > On Dec 18, 2023, at 7:13 PM, Mihai Budiu wrote: >

Re: warnings in Calcite

All these cases where at compile time an exception is thrown and caught could be warnings - e.g. Casts that will fail at runtime, division by 0, etc. Mihai From: Julian Hyde Sent: Monday, December 18, 2023 10:41:11 PM To: dev@calcite.apache.org Subject: Re:

Re: Case-sensitive parser configuration for quoted identifiers

Hi Julian Thanks for the response on this and suggesting use of QUOTED_CASING and UNQUOTED_CASING properties. The values for these properties are either TO_LOWER, TO_UPPER or UNCHANGED. But I don't not find an option which records if the identifier was quoted/not. This information is being