Thanks Stamatis, that makes sense. I'll keep using it as shown in those
examples then.
Best,
Nicola
Il giorno lun 7 feb 2022 alle ore 22:52 Stamatis Zampetakis <
zabe...@gmail.com> ha scritto:
> Hey Nicola,
>
> If you need a way to combine operators from the Enumerable convention,
> which
Hey Nicola,
If you need a way to combine operators from the Enumerable convention,
which generate Java code, with other kind operators you need to have some
common interfaces to pass from one to the other.
The XToEnumerableConverter needs to know how to generate code calling the
operators of the
I've seen that in many adapters, although they implement the
TranslatableTable interface, Queryable is still used (see the usage of
table.getExpression(...) in XToEnumerableConverter for Elasticsearch,
Mongo, and Geode, to name a few). What is the reasoning there?
Il giorno mar 25 gen 2022 alle
+1 what Stamatis said. Queryable is for compatibility with LINQ. If you want to
build an adapter that supports push-down, you will likely use FilterableTable
for simple adapters, TranslatableTable for more complex adapters. In neither
case will you need to deal with Queryable.
Stamatis laid
Hi Julian,
I don't think there is an easy way to understand the Queryable interface
unless you check how it is used. I don't see it as something that you need
to implement no matter what but more as a convenience API that will
facilitate the integration with the Enumerable operators (if you rely
Hi all,
in the last weeks I worked on Integrating the Apache IoTDB Project with Calcite.
This covers two possible scenarios. One, to use Apache IoTDB as an Adapter in
Apache Calcite (like MongoDB, Cassandra, et al) and on the other hand we are
looking at using Calcites Query Optimizer to
