Hmm. In that case I'm not sure why we came to the belief that newer Calcites
could not be used with Guava 16.0.1. Maybe it was from reading the Calcite
release notes rather than actually testing it. It would be great if this just
works.
I raised this PR:
Gian Merlino created CALCITE-5428:
-
Summary: Reduce minimum Guava version to 16.0.1.
Key: CALCITE-5428
URL: https://issues.apache.org/jira/browse/CALCITE-5428
Project: Calcite
Issue Type:
I ran with '-Dguava.version=16.0.1' and it seems to just work.
If you want this to be the new minimum, please create a Jira case and
PR. Changes will be needed to main.yml (GitHub CI), comments in
gradle.properties, and history.md (release notes for the upcoming
release).
Julian
On Fri, Dec 9,
If Calcite ends up dropping the minimum to 16, that would certainly be helpful,
and appreciated, since it would mean Druid can upgrade Calcite without needing
to also tackle the Hadoop 2 problem. Please let us know if it seems like that
would be in the cards!
In case Calcite sticks on Guava
Hi all,
thanks Stamatis for the proposal and the work, I am a huge fan of Sonar and
I really miss it on Calcite, so a big +1 from me on this.
In Hive so far we have received good feedback, so I hope it will be
welcomed here too.
Best regards,
Alessandro
On Fri, 9 Dec 2022 at 19:02, Stamatis
Hi all,
I just logged CALCITE-5427 [1] for introducing code quality & coverage
metrics in Calcite CI.
I added some motivation and examples under the ticket so please have a look
and let me know what you think.
If there are no objections, I will follow-up with INFRA to set things up
for the
Stamatis Zampetakis created CALCITE-5427:
Summary: Provide code quality/coverage metrics with SonarCloud and
JaCoCo
Key: CALCITE-5427
URL: https://issues.apache.org/jira/browse/CALCITE-5427
Dmitry Sysolyatin created CALCITE-5426:
--
Summary: BlockBuilder should not reuse mutable objects
Key: CALCITE-5426
URL: https://issues.apache.org/jira/browse/CALCITE-5426
Project: Calcite
