IMO the main benefit is to inherit the optimization of spark SQL(such as
whole stage codegen, memory management, maybe vectorized execution in
future ...).
not farmilar with calcite's codegen mechanism, any reference about it?
I think firstly i will unsterstand how the spark adapter now
Francis Chuang created CALCITE-1369:
---
Summary: Display a list of Avatica clients on the website
Key: CALCITE-1369
URL: https://issues.apache.org/jira/browse/CALCITE-1369
Project: Calcite
All,
I'm happy to welcome Francis as an Apache Calcite committer. This is in
recognition of Francis' continued contributions to the project, most
notably in support of the development and stability of Avatica. Francis
has been a great source of help for Avatica, reporting numerous issues
It’s an interesting idea. I know that the data frame API is easier to work with
for application developers, but since Calcite would be generating the code, can
you describe the benefits to the Calcite user of changing the integration point?
It’s definitely true that Calcite’s Spark adapter
On behalf of the PMC I am delighted to announce MinJi Kim as a new Calcite
committer. Over several months MinJi has contributed more than a few patches to
the planner and adapters, always high quality and well tested, and it has been
a pleasure interacting with her. Please give MinJi a warm
Forwarding to Calcite dev. I have heard that people are working on a Calcite
adapter for DynamoDB and Calcite adapters can often be used in Drill.
Julian
> On Sep 4, 2016, at 12:03 PM, Navin Viswanath wrote:
>
> Hi,
>
> I'm currently working on a tool that provides a