[jira] [Created] (CALCITE-2249) AggregateJoinTransposeRule generates inequivalent nodes if Aggregate relNode contains distinct aggregate function.

jingzhang created CALCITE-2249: -- Summary: AggregateJoinTransposeRule generates inequivalent nodes if Aggregate relNode contains distinct aggregate function. Key: CALCITE-2249 URL:

Calcite-Master - Build # 251 - Still Failing

The Apache Jenkins build system has built Calcite-Master (build #251) Status: Still Failing Check console output at https://builds.apache.org/job/Calcite-Master/251/ to view the results.

Re: Lineage graph from Queries

Thanks for the quick response Enrico. >> Not sure if I understand correctly, but you are looking for something that given an SQL statement and metadata about existing tables it returns one (or more) access plan ? Yes, we are looking for table/DB object level plan Just for example, in the case

Lineage graph from Queries

Hi All, I am new to calcite. Need your help/inputs on usage of calcite to solve one of our use case. We need to build a library to get the lineage graph of given query. Here given query can be either Hive/ANSI SQL/Vertica queries etc. We can build this library by using their respective physical

Re: Lineage graph from Queries

Il mer 11 apr 2018, 22:34 AnilKumar B ha scritto: > Hi All, > > I am new to calcite. Need your help/inputs on usage of calcite to solve one > of our use case. > > We need to build a library to get the lineage graph of given query. Here > given query can be either Hive/ANSI

[newbie]Help needed wrt execute a query in parallel

Hi All, I am new to calcite. I need help to implement an "Exchange operator" in calcite. I read the Research Paper " Apache Calcite:A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources " for a mere understanding of calcite. An Exchange operator basically

Re: Lineage graph from Queries

Thanks for the help Julian. By lineage we mean given a query as an input to the API , we would like to get *input table list* and *output table* as the output (Intermediate temp tables are optional in lineage). Below are few examples in hive and in vertica *Hive Example :* FROM page_view_stg pvs