> [...] I wanted to get a better idea what circumstances cause it.
In this particular case I came across this failure while experimenting with
SQL support in Stargate [1], which uses Apache Cassandra for storage and
Cassandra's float type is actually 32-bit [2], so it naturally maps to java
I guess this happened because, as you say, 'float' and 'char' never
happen in the JDBC world. The next question is: do they ever
legitimately occur in the SQL world?
To be clear, this sounds like this is a bug, and I think we should fix
it, but I wanted to get a better idea what circumstances
> CALCITE-1490 suggests only add to SQL server, but as Oracle, Snowflake and
> BigQuery seems all support the simplified syntax, it might be enough to
> justify adding this support to default syntax?
Possibly, but I'd be cautious, because the semantics become ambiguous
if there are name clashes.
Hello,
I noticed that if the rows passed to org.apache.calcite.avatica.Meta.Frame
contain Float values, the following exception [1] occurs when the frame is
sent to the client with PROTOBUF serialization.
Would this be considered a valid use case?
I can only reproduce it in unit tests or with
>Are we planning to support it as a default syntax or as a dialect ? Say,
>maybe Oracle.
CALCITE-1490 suggests only add to SQL server, but as Oracle, Snowflake and
BigQuery seems all support the simplified syntax, it might be enough to
justify adding this support to default syntax?
>Another idea
Chunwei Lei created CALCITE-4368:
Summary: TopDownOptTest fails if applying non-substitution rule
first
Key: CALCITE-4368
URL: https://issues.apache.org/jira/browse/CALCITE-4368
Project: Calcite
