[jira] [Created] (CALCITE-4984) RelNode decorrelations is generating wrong group keys

2022-01-11 Thread Shiven Dvrk (Jira)
Shiven Dvrk created CALCITE-4984: Summary: RelNode decorrelations is generating wrong group keys Key: CALCITE-4984 URL: https://issues.apache.org/jira/browse/CALCITE-4984 Project: Calcite Iss

Re: Calcite-Clojure integration - use Clojure to implement calcite back-ends

2022-01-11 Thread Eugen Stan
Hello Stamatis, I sent my proposal on the original meeting thread. Forgot to ask: What is the exact day of the event? I see January 19 mentioned here: https://www.meetup.com/Apache-Calcite/events/282836907/ And you mentioned January 17 on this email. Regards, -- Eugen Stan +40770 941 271

Re: Re: [DISCUSS] Apache Calcite Online Meetup January 2022

2022-01-11 Thread Ioan Eugen Stan
Hello Stamatis, I would also like to share my work. Title: calcite-clj - First steps using Calcite with Clojure Abstract: A quick introduction on using Calcite with Clojure language. I'll go through an simple example on how to use in memory table. The example will cover REPL driven developmen

Re: [DISCUSS] Draft board report for Jan 2022

2022-01-11 Thread Michael Mior
Thanks Haisheng! Looks good to me. -- Michael Mior mm...@apache.org Le ven. 7 janv. 2022 à 12:32, Haisheng Yuan a écrit : > Attached below is a draft of this month's board report. I plan to submit it > on Jan 11. > Please let me know if you have additions or corrections. > > ## Description: >

[jira] [Created] (CALCITE-4983) In SubstitutionVisitor, create a Calc when there has condition need pull up.

2022-01-11 Thread Ziwei Liu (Jira)
Ziwei Liu created CALCITE-4983: -- Summary: In SubstitutionVisitor, create a Calc when there has condition need pull up. Key: CALCITE-4983 URL: https://issues.apache.org/jira/browse/CALCITE-4983 Project: C

Re: Apache Calcite - Generated code

2022-01-11 Thread M Singh
Thanks Ruben for pointing me to the answer.  I was not subscribed to the dev list at that time and so missed this response.   Thanks again for your help.On Tuesday, January 11, 2022, 08:29:50 AM EST, Ruben Q L wrote: Hello, if I am not mistaken, there were already some answers to you

Re: Sort getting removed during optimization

2022-01-11 Thread Julian Feinauer
Hey Vladimir, when this issue appeared it was RelTraitSet desired = cluster.traitSet() .replace(BindableConvention.INSTANCE); RelNode expectedRoot = planner.changeTraits(root, desired); planner.setRoot(expectedRoot); And then RelNode exp = planner.findBestExp(); So the root node had no s

Re: Fw: Apache Calcite - Generated code

2022-01-11 Thread Ruben Q L
Hello, if I am not mistaken, there were already some answers to your original email, please check https://lists.apache.org/thread/xghcjo5xwn04ylyow5h7to507ts91qs3 Best regards, Ruben On Tue, Jan 11, 2022 at 1:09 PM M Singh wrote: > Hi folks: > I apologize for sending the message again but wa

Fw: Apache Calcite - Generated code

2022-01-11 Thread M Singh
Hi folks:  I apologize for sending the message again but wanted to see if there is any advice/pointers on understanding Calcite code generation.   If I have missed the response, please forward it to one more time. Thanks again for your help. Mans Hi: I am working on a project that requires chan

Re: Apache Calcite - Understanding Translatable table

2022-01-11 Thread M Singh
Thanks Jess for your pointers.  I will checkout the references you have provided.  Mans On Sunday, January 9, 2022, 06:01:47 PM EST, Jess Balint wrote: Hi Mans, This statement in the Javadoc sums it up for me:     Generally a Table will implement this interface to create a particular

Re: Different behavior bewteen '>' and '='

2022-01-11 Thread Vladimir Ozerov
Hi, If I recall correctly, the SQL standard is mostly silent on how one should coerce operands. Therefore different systems implement the coercion at their discretion. Moreover, the type inference might be influenced not only by operands types but by their nature as well. For example, a target sys

Re: Sort getting removed during optimization

2022-01-11 Thread Vladimir Ozerov
Hi Julian, When invoking the optimizer, you may provide the desired trait set of the top-level node. It might happen, that the specific collation is not requested from the optimizer, and hence the plan with a top-level Sort operator is not chosen. Could you please show how you invoke the planner?

Re: Sort getting removed during optimization

2022-01-11 Thread Julian Feinauer
Hey Stamatis, yes, thats why I looked it up at first… the results are wrong : ) So both tables for themselves are sorted but the Full Join is finally two blocks. The Left Join (sorted like the left rel) and then the remaining entries from the right side (also ordered). But overall not ordered.

Re: Sort getting removed during optimization

2022-01-11 Thread Stamatis Zampetakis
Hi Julian F, Quite a naive question but did you get wrong results from the given plan? A missing sort is not necessarily problematic. I hope I am not saying something stupid but I think there are cases where a full join algorithm can retain the order of some of its inputs. Best, Stamatis On Tue