As of Apache Calcite Avatica 1.9.0, there are two artifacts (jars) provided that enable client-access
to an Avatica server over JDBC.
In keeping with the convention of previous releases, org.apache.calcite.avatica:avatica is a JAR
which contains all of the necessary dependencies of the Avatica client code base. Those classes which
can be safely relocated are done so to reduce the potential for classpath issues.
Avatica 1.9.0 will introduce a new artifact org.apache.calcite.avatica:avatica-core which is only
the Avatica client classes without any bundled dependencies. This artifact enables users to build a
classpath with different versions of JARs than what Avatica presently depends upon. This is a “your-mileage-may-vary”
or “void-your-warranty” type of decision (as you are using Avatica with dependecies which we have not tested);
however, some downstream projects do provide reasonable assurances of compatibilities across releases.
Building your own Avatica client artifact
In some cases, it may be beneficial to provide specific versions of Avatica dependencies. Here is
a brief pom.xml which outlines how this can be done.