Can`t build master of calcite.

hi ! can`t build top of calcite (sha: commit 74e97780add051cb71a122075e5bcbceb) $ ./gradlew build Task :core:compileJava /home/zstan/work/repo/calcite/core/src/main/java/org/apache/calcite/prepare/PlannerImpl.java:39: warning: [deprecation] org.apache.calcite.rel.metadata.CachingRelMetada

Re: [VOTE] Release apache-calcite-avatica-1.19.0 (release candidate 0)

My vote is: +1 (Thanks Julian!) - Verified GPG signature - OK - Verified SHA512 - OK - Checked release notes on stage branch (https://github.com/apache/calcite-avatica/blob/stage/site/_docs/history.md) - OK - Ran tests (gradle test) - OK - Spot checked Nexus artifacts - OK Notes: - The build

Lots of warnings with latest gradle?

Hey all, Calcite master has the latest gradle in it now. It seems like I'm seeing a lot of warnings like: https://gist.github.com/jacques-n/910b917f52cbf8dda22b2749ef0ea6b6 Are others seeing that as well? Do we have a ticket to address (quick search didn't find one)? It makes it much harder to se

[VOTE] Release apache-calcite-avatica-1.19.0 (release candidate 0)

Hi all, I have created a build for Apache Calcite Avatica 1.19.0, release candidate 0. Thanks to everyone who has contributed to this release. And thank you to Francis, Vladimir and Stamatis for assistance with the release process. You can read the release notes here: https://gitbox.apache.org/r

[jira] [Created] (CALCITE-4831) Cleanup Nullable rule annotations post fix for Immutables checker conflict bug

Jacques Nadeau created CALCITE-4831: --- Summary: Cleanup Nullable rule annotations post fix for Immutables checker conflict bug Key: CALCITE-4831 URL: https://issues.apache.org/jira/browse/CALCITE-4831

[jira] [Created] (CALCITE-4830) Move Cassandra module to use Immutables instead of ImmutableBeans

Jacques Nadeau created CALCITE-4830: --- Summary: Move Cassandra module to use Immutables instead of ImmutableBeans Key: CALCITE-4830 URL: https://issues.apache.org/jira/browse/CALCITE-4830 Project: Ca

Re: (CALCITE-4292) Wrong results in ElasticSearch when query contains NOT EQUAL

I also agree that we should preserve SQL semantics, regardless of the adapter. For more details see a good article about Three Valued Logic . On Tue, Oct 5, 2021 at 11:32 AM Julian Hyde wrote: > I support Stamatis’ position. Our SQL adapter mus

Re: (CALCITE-4292) Wrong results in ElasticSearch when query contains NOT EQUAL

I support Stamatis’ position. Our SQL adapter must implement SQL semantics. That is what users of a SQL interface want and expect. If Elasticsearch’s data model has nuances that cannot be captured in SQL, feel free to add extra operators. If name is a multi-valued attribute, then some ideas ar

Re: (CALCITE-4292) Wrong results in ElasticSearch when query contains NOT EQUAL

Hi all, The question is basically how the following SQL statement should behave for rows where the name is NULL in the ElasticSearch adapter. SELECT * from zips WHERE name <> "NMAX" I did add my comments in the JIRA case but it would be good if somebody also expresses an opinion so that we resol

[jira] [Created] (CALCITE-4829) Bump Gradle to 7.2 and test with Java 17 at GitHub Actions

Vladimir Sitnikov created CALCITE-4829: -- Summary: Bump Gradle to 7.2 and test with Java 17 at GitHub Actions Key: CALCITE-4829 URL: https://issues.apache.org/jira/browse/CALCITE-4829 Project: Calc

Re: Avatica dry-run

Yes, docker should give you a clean slate every time you use it (with the exception of the gradle-cache volume to speed things up by reusing the cached items), so I am not quite sure why it's causing a permission issue with the home directory on your machine. As for the passwords in a single t

Re: Avatica dry-run

I thought the purpose of using Docker was to create a simpler, more reproducible environment. I don't use Docker regularly (in fact, my employer bans it from my work machine) and so, from my perspective, any use of Docker makes the process more complicated. I also hate having to put all of my most

Re: Avatica dry-run

Hey Julian, Thanks for reporting that. I think the instructions in the howto needs to be clearer regarding the steps to start asflike-release-environment. I think we should put the actual commands used to start the mock servers directly in there. Hmm, the docker build should not write to you

Re: Avatica dry-run

Francis, That helped somewhat. I was able to get the Docker-powered server running using your instructions. (From reading the HOWTO, I had no idea that I was creating a server in a separate terminal.) I was running Tomcat on port 80, and so I had to shut that down to prevent port clashes. But the