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 private and specific to the JDBC adapter, but looking at the code base, I see it used in lots of various places. Has the policy changed? if so, would it make sense to change it to an interface or to relax the class? The current model where all informations are stored in maps doesn't match our own model of navigating our catalog. Cheers, Laurent
