Sorry, I misinterpreted your last message. As for Dremio/Drill, the model
offered by CalciteSchema is not scalable as it requires all subschemas and
tables to be loaded, even if only one table is accessed: fetching all
metadata might be an expensive operation depending on the type and number
of
That was my understanding, but it seems usage of CalciteSchema is prevalent
outside the scope of the JDBC adapter:
$ grep -rl import.*CalciteSchema core/src/main/java|grep -v calcite/jdbc
core/src/main/java/org/apache/calcite/materialize/Lattice.java
The policy that CalciteSchema should be private to Calcite hasn’t changed (it
is a public interface only because… Java).
It has never been private to the JDBC adapter. (The JDBC adapter readers from
JDBC sources and is in org.apache.calcite.adapter.jdbc, whereas CalciteSchema
is in
Hi,
While working on rebasing our code on top of Calcite 1.16, I noticed that a
new method was introduced to SqlValidatorCatalogReader: CalciteSchema
`SqlValidatorCatalogReader#getRootSchema()` (not recently, it was added for
Calcite 1.12)
My understanding of CalciteSchema was that this class is
