Re: Quicksql

ke query executed on > >> different data source? > >> > >> > >> Yes, virtualization is one of Calcite’s goals. In fact, when I created > >> Calcite I was thinking about virtualization + in-memory materialized > >> views. > >> Not only the Spark convention but any o

Re: Quicksql

Basically, i like and agree with Julian’s statement. It is a great idea >> which personally hope Calcite move towards. >> >> >> Give my best wishes to Calcite community. >> >> >> Thanks, >> Trista >> >> >> Juan Pan >> >> >> panj...@apache.org >> Juan Pan(Trista

Re: Quicksql

ingSphere > > > On 12/11/2019 10:53，Haisheng Yuan wrote： > As far as I know, users still need to register tables from other data > sources before querying it. QuickSQL uses Calcite for parsing queries and > optimizing logical expressions with several transformation rules. The query

Re: Quicksql

different data source will then be registered as temp spark tables (with filter or join pushed in), the whole query is rewritten as SQL text over these temp tables and submitted to Spark. - Haisheng -- 发件人：Rui Wang 日 期：2019年12月11日 06:24:45 收件人： 主

Re: Quicksql

sources before querying it. QuickSQL uses Calcite for parsing queries and > optimizing logical expressions with several transformation rules. The query > on different data source will then be registered as temp spark tables (with > filter or join pushed in), the whole query is rewritten as S

Re: Quicksql

ferent data source will then be registered as temp spark tables (with filter or join pushed in), the whole query is rewritten as SQL text over these temp tables and submitted to Spark. - Haisheng -- 发件人：Rui Wang 日 期：2019年12月11日 06

Re: Quicksql

written as SQL text over these temp tables and submitted to Spark. - Haisheng -- 发件人：Rui Wang 日　期：2019年12月11日 06:24:45 收件人： 主　题：Re: Quicksql The co-routine model sounds fitting into Streaming cases well. I was thinking how sho

Re: Quicksql

- 发件人：Rui Wang 日 期：2019年12月11日 06:24:45 收件人： 主 题：Re: Quicksql The co-routine model sounds fitting into Streaming cases well. I was thinking how should Enumerable interface work with streaming cases but now I should also check Interpreter. -Rui On Tue, Dec 10, 2019 at 1:33 PM Julian Hyde wr

Re: Quicksql

ll then be registered as temp spark tables (with > filter or join pushed in), the whole query is rewritten as SQL text over > these temp tables and submitted to Spark. > > > > - Haisheng > > > > -- > >

Re: Quicksql

park tables (with filter or join > pushed in), the whole query is rewritten as SQL text over these temp tables > and submitted to Spark. > > - Haisheng > > -- > 发件人：Rui Wang > 日　期：2019年12月11日 06:24:45 > 收件人： > 主　

Re: Quicksql

ll then be registered as temp spark tables (with filter or join pushed in), the whole query is rewritten as SQL text over these temp tables and submitted to Spark. - Haisheng -- 发件人：Rui Wang 日　期：2019年12月11日 06:24:45 收件人： 主　题：Re: Qui

Re: Re: Quicksql

(with filter or join pushed in), the whole query is rewritten as SQL text over these temp tables and submitted to Spark. - Haisheng -- 发件人：Rui Wang 日　期：2019年12月11日 06:24:45 收件人： 主　题：Re: Quicksql The co-routine model sounds fitting

Re: Quicksql

The co-routine model sounds fitting into Streaming cases well. I was thinking how should Enumerable interface work with streaming cases but now I should also check Interpreter. -Rui On Tue, Dec 10, 2019 at 1:33 PM Julian Hyde wrote: > The goal (or rather my goal) for the interpreter is to

Re: Quicksql

The goal (or rather my goal) for the interpreter is to replace Enumerable as the quick, easy default convention. Enumerable is efficient but not that efficient (compared to engines that work on off-heap data representing batches of records). And because it generates java byte code there is a

Re: Quicksql

What is the ultimate goal of the Calcite Interpreter? To provide some context, I have been playing around with calcite + REST (see https://github.com/zolyfarkas/jaxrs-spf4j-demo/wiki/AvroCalciteRest for detail of my

Re: Quicksql

The guys at Contiamo [1] are doing similar stuff. I added the nice talk [2] by Chris in ApacheCon to our website. [1] https://www.contiamo.com/ [2] https://youtu.be/4JAOkLKrcYE On Tue, Dec 10, 2019 at 3:05 AM Julian Hyde wrote: > Yes, virtualization is one of Calcite’s goals. In fact, when I

Re: Quicksql

Yes, virtualization is one of Calcite’s goals. In fact, when I created Calcite I was thinking about virtualization + in-memory materialized views. Not only the Spark convention but any of the “engine” conventions (Drill, Flink, Beam, Enumerable) could be used to create a virtual query engine.

Re: Quicksql

I recently contacted one of the active contributors asking about the purpose of the project and here's his reply: >From my understanding, Quicksql is a data virtualization platform. It can > query multiple data sources altogether and in a distributed way; Say, you > can write a SQL with a MySql