Julian Hyde created CALCITE-6408:
Summary: Not-null ThreadLocal
Key: CALCITE-6408
URL: https://issues.apache.org/jira/browse/CALCITE-6408
Project: Calcite
Issue Type: Improvement
Hi Stamatis,
Thanks for the quick reply, this seems to be exactly what I was looking
for! Is there any literature / articles you could recommend on this topic
of optimizations and preprocessing? I've found reading through Calcite docs
and source code to be a tad tedious, and wondering if there is
Mihai Budiu created CALCITE-6407:
Summary: DECIMAL types with scale > precision should be tested
Key: CALCITE-6407
URL: https://issues.apache.org/jira/browse/CALCITE-6407
Project: Calcite
Iss
Mihai Budiu created CALCITE-6406:
Summary: Negative scales for DECIMAL types are not tested
Key: CALCITE-6406
URL: https://issues.apache.org/jira/browse/CALCITE-6406
Project: Calcite
Issue Ty
Oleg Alekseev created CALCITE-6405:
--
Summary: TO_TIMESTAMP doesn't work
Key: CALCITE-6405
URL: https://issues.apache.org/jira/browse/CALCITE-6405
Project: Calcite
Issue Type: Bug
Hey Logan,
Many parts of Calcite such as rules and metadata providers rely on the
assumption that the RelNode tree does not contain subqueries. This is
achieved by using the SubQueryRemoveRule [1] early on during the
optimization process. Another pretty common preprocessing step is
query decorrela