I am not an expert on Java builds, but here is one way you can do it.
We build our compiler using the current main branch of Calcite.
We use 4 components from calcite, so I wrote the following script which
installs locally the artifacts needed:
GROUP=org.apache.calcite
VERSION=1.40.0
cd ~/git/calcite
./gradlew build -x test
for DIR in core babel server linq4j
do
ARTIFACT=calcite-${DIR}
mvn install:install-file
-Dfile=${DIR}/build/libs/${ARTIFACT}-${VERSION}-SNAPSHOT.jar -DgroupId=${GROUP}
-DartifactId=${ARTIFACT} -Dversion=${VERSION} -Dpackaging=jar -DgeneratePom=true
done
In our compiler in the pom files (we still use maven) we use the same version
of Calcite (1.40.0), which is yet unreleased, so there is no danger that it
will be downloaded from maven central.
Mihai
________________________________
From: Alessandro Solimando
Sent: Wednesday, May 7, 2025 1:46 AM
To: dev@calcite.apache.org
Subject: Re: Inquiry About Upcoming Release Timeline Including Trino Dialect
Support (PR #4249)
Hi Eden,
I will be the next release manager and I am planning to start the next
release process at the end of May / beginning of June, as Ruben said.
In the meantime, you can start testing the latest snapshot version in your
downstream project, which is also a good way to spot and report issues
early on. Ideally, one could even run one (private) CI pipeline for the
downstream project daily against the latest snapshot to constantly monitor
regressions.
I have never integrated the daily snapshots myself but I found an example
for ActiveMQ and Maven that might help you out with that:
https://activemq.apache.org/components/classic/documentation/maven-snapshot-repository-in-your-pom
Here is where the snapshots associated with the current main branch are
being published by the CI pipeline:
https://repository.apache.org/content/repositories/snapshots/org/apache/calcite/
If you find out that a given snapshot version works for you, you could
consider pushing that specific version to an internal maven repository so
you have more control over what happens (you could "pin" a specific version
from the daily snapshots).
Best regards,
Alessandro
On Wed, 7 May 2025 at 10:12, eden kiknadze <edenkiknadze2...@gmail.com>
wrote:
> Hey,
>
> I've been working on a project that involves parsing Trino queries using
> Apache Calcite. While doing so, I encountered issues parsing Trino-style
> DDL queries, such as: org.apache.calcite.sql.parser.ddl.ParseException:
> Encountered "WITH" ... was expecting one of: <EOF>
>
> While researching, I came across PR #4249
> <https://github.com/apache/calcite/pull/4249>, which appears to add
> support
> for Trino-specific dialect features. This is exactly the functionality I
> was hoping to use.
> I noticed that Calcite’s last release was in March, and historically the
> release cadence is every 5 months. I’m writing to ask whether there’s any
> upcoming release planned that will include this PR, or if there’s a
> recommended approach for using the Trino dialect support ahead of time.
>
> Thank you.
>
