Bertil Chapuis created CALCITE-6239:
---
Summary: Add a postgis dialect that supports ST functions
Key: CALCITE-6239
URL: https://issues.apache.org/jira/browse/CALCITE-6239
Project: Calcite
Mihai Budiu created CALCITE-6238:
Summary: Exception while evaluating ROUND function
Key: CALCITE-6238
URL: https://issues.apache.org/jira/browse/CALCITE-6238
Project: Calcite
Issue Type:
That method is intended if you have a class MyTableScan and a generic rule that
can handle any instance of MyTableScan.
If you have (say) five instances of MyTableScan and five rule instances, one
for each scan, then you should register each rule instance individually in the
planner.
There
Hi Bertil,
Let me explain a bit about Drill and Calcite. Drill uses Calcite for query
planning. Until fairly recently, Drill had a fork of Calcite that had some
special features which Drill required. However, about 1-2 versions ago, we
were able to get Drill off of the fork an onto
Hello Calcite devs,
Our team currently has a setup in which we have a single TableScan
implementation (e.g. MyTableScan) serving multiple Calcite tables. Each
MyTableScan handles the registration of rules tailored to its respective
Calcite table. I've included an example of the code structure at
Thanks for picking this up. One of my students and myself wrote a lot of
the original code. For a while this was blocked on necessary changes to
Apache Arrow, but this has since been resolved. I'd love to see this get
merged. It would help to rebase into a single commit. I'd also appreciate
one
Hi devs,
Recently I found a [CALCITE-2040] "Create adapter for Apache Arrow"[1] that
is almost finished in PR#2810[2], but no one continues to push it forward,
so I want to take it. I made some changes to the existing PR, including
- Upgrade arrow to 15.0
- Prohibit arrow adapter CI on Windows
