Dear all, I am exploring Calcite and, as a study use case, I am trying to create a JDBC interface to a non-relational database that has its own joins, aggregates, etc. I have been playing with a TranslatableTable and some planner rules, but given that basically all queries including joins would be pushed down to the underlying engine, I am wondering whether an adapter (like the core JDBC) would still be the preferred route or a different approach (custom JDBC driver + query rewriting engine maybe?) is advised. What would you recommend?
Thanks, Nicola
