Thanks for the update, Jordan. I’m still hopeful that it will happen. There is
a lot of demand for Calcite-on-Spark (and apparently people willing to
contribute) and this code donation would focus those efforts.
Julian
> On May 31, 2017, at 3:42 PM, Jordan Halterman
> wrote:
>
> I left Data
I left DataScience a few months ago to go lead distributed systems work at the
Open Networking Laboratory. Originally, the week I left they said they intended
to open source it, but that never happened. I no longer have control over the
project, but I’m still in touch with my old partner in crim
Hi Jordan,
Just want to check if you guys have any plan to contribute back the work of
converting back and forth between Calcite and Spark/Catalyst plans?
Thanks,
Khai
On Thu, Feb 16, 2017 at 3:42 PM, jordan.halter...@gmail.com <
jordan.halter...@gmail.com> wrote:
> Calcite differs from Catalyst
Calcite differs from Catalyst in many ways. First of all, Catalyst is
essentially a heuristic optimizer, while Calcite optimizers often combine
heuristics and cost-based optimization. Catalyst pushes down predicates and
projections to most data sources, while Calcite can often push down full
qu
Heya,
I've been using Spark recently and have stumbled across a couple surprising
bugs/feature gaps. It got me curious about how Calcite would handle the
same scenarios. Basically, I'm wondering if Calcite would handle these
scenarios directly or if it would defer to the underlying runtime. I.E.,
