In the second approach, where would the Cassandra prepared statement be
stored? I'm not sure I understand the lifecycle of Calcite statements. Is
there ever a case where the same statement will be reused? If there's a
convenient object to attach the Cassandra prepared statement to, that's
great.
I don’t recall whether there is a convenient “hook” in the adapter that gets
called when Calcite prepares a statement. Maybe after the best plan has been
found, and a CassandraRel.Implementor has finished walking over a tree of
CassandraRel nodes the Implementor could send the statement to
When would be a good time for the next Calcite release? Do we want to make an
Avatica release before the Calcite release?
A couple of ideas:
* I was thinking of releasing Calcite last week of August. (Last release was
13th June, so it would be 2 1/2 months.)
* Avatica seems to have been fairly
Great! Looking forward to reviewing the PR. Unfortunately I'm not really
familiar with the PreparedStatement implementation in Calcite but I don't
believe it's currently possible to implement adapter-specific behaviour
prepared statements. At this point I think preparing statements only serves
to
Julian Hyde created CALCITE-1345:
Summary: Streaming GROUP BY
Key: CALCITE-1345
URL: https://issues.apache.org/jira/browse/CALCITE-1345
Project: Calcite
Issue Type: Bug
Reporter:
Jesus Camacho Rodriguez created CALCITE-1344:
Summary: Incorrect inferred precision when BigDecimal value is
less than 1
Key: CALCITE-1344
URL: https://issues.apache.org/jira/browse/CALCITE-1344
