Hi,

I am just in the process of updating to the latest version of calcite for my project and have run into an issue and not sure whether I am missing something.

I currently use a process based on some of the code around MockCatalogReader to create a catalog and allow my sql to get parsed to relational algebra, which is all I use from the calcite side of things.

I was able to dynamically look up metadata previously in the code by having the CatalogReader getTable code lazily load the metadata items as it received request for tables.

It seems with the 1.12 code and the requirement to use calciteSchema it expects all the schemas and tables to be available all the time.

I am wondering if my lazy load approach is a mistake or if I should work on the calciteSchema interface to allow it to continue with this behaviour.

Does anyone have thoughts on if what I am trying to do makes sense.

thanks


Reply via email to