Hi, I've been working lately on Apache Calcite SQL/JDBC adapter for Apache Geode [1].
Adapter's current implementation act as a plain Geode client (using the public API/OQL interfaces) trying to push down to Geode OQL as many relational expressions as it can. Relational expressions not supported by OQL are executed by the adapter itself. While this approach has its advantages and disadvantages, which I will try to address at my Geode Summit talk [2] I would like to ask two question: 1. Would you be interested to have the adapter as part of Geode's code ecosystem? 2. I am aware (an experienced it myself) the SQLFire story. But given that OQL features are expanding (aggregations are are already supported) and that tools like Calcite offer proper logical/physical (cost based) planer and SQL extensions such as SQL streaming, would it be useful to discuss what novel approaches for using SQL/JDBC with Geode are possible? (Julian Hyde - founder of Calcite - is in cc) Cheers, Christian [1] https://github.com/tzolov/calcite/tree/geode-1.3 [2] https://springoneplatform.io/sessions/enable-sql-jdbc-access-to-apache-geode-gemfire-using-apache-calcite -- Christian Tzolov <http://www.linkedin.com/in/tzolov> | Principle Software Engineer | Pivotal <http://pivotal.io/> | ctzo...@pivotal.io |+31610285517
