The avatica jar includes a shaded version of jackson under the original package path.
This shaded version interferes with other jackson versions in the classpath.
Currently this prevents us from using jackson functionality which is only implemented in newer versions.
Is it reasonable to have a maven profile that uses jackson as “provided” rather than shading? This would not be the default — the default would be continue to use a shaded version of jackson (relocated to org.apache.calcite.jackson, as Josh suggests) — but folks looking to embed calcite/avatica in a container might appreciate a lighter weight option.