geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Huynh <>
Subject Re: [Discussion] SQL+Streaming/JDBC as one of the unified interfaces
Date Mon, 13 Nov 2017 18:46:46 GMT
Hi Christian,

I don't know much about Calcite and haven't had a chance to try out your
adapter yet but it sounds like a neat idea.  Will your talk be recorded and
available after the Summit?

Also for question 1. Would you be interested to have the adapter as part of
Geode's code ecosystem?
Do you mean to create a module in Geode for this adapter?  Would it make
sense to add a Geode module to Calcite?  Were you wanting a tighter
integration (beyond an adapter) with Calcite within Geode?


On Fri, Nov 10, 2017 at 3:49 AM Christian Tzolov <> wrote:

> 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]
> [2]
> --
> Christian Tzolov <> | Principle Software
> Engineer | Pivotal <> | |+31610285517
> <+31%206%2010285517>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message