Hello,
I have logged a Jira ticket for this:
https://issues.apache.org/jira/browse/CALCITE-3465
I have listed all the data types for Cassandra 3.x, and I have tried to
compile a table with the current status, but there are few entries for
which I am not sure.
If you have time to contribute to
I think it's me who does not have to understand all the subtlety.
I thought that STREAM works more like a in-memory- relational database
but i missed something thank for your help :)
Le jeu. 17 oct. 2019 à 15:53, Michael Mior a écrit :
> Perhaps I'm missing something, but I don't see why this
Perhaps I'm missing something, but I don't see why this would be any
more efficient. Selecting all data is also not an efficient operation
in Cassandra. Using ALLOW FILTERING will likely be more efficient
since it's basically the same as doing a table scan, but it avoids
returning data which would
Thank for reply Michael.
yes i understood this on the documentation for example with "WHERE"
statement calcite i force the . "ALLOW FILTERING; "
and this can be expensive.
I think there may be an interesting approach using STREAM.
for example maintain a regular update between a cassandra
You're right that there are several types which are not supported by
the Cassandra adapter. We would happily accept pull requests to add
support for new types.
You're also correct that Cassandra cannot efficiently execute queries
which do not specify the partition key. Calcite will make those
Hi guys ,
I study Calcite the benefits that a Cassandra-Calcite Adapter can bring ,
as for example brings the possibility of join.
the problem type defined into CassandraSchema.getRelDataType(..) is very
limited
some important type are missing boolean / array ect...
I thought inherited from
