Thanks Julian and Austin! Any reply to kick-off some sort of discussion is worthwhile :D I definitely know the feeling of having more PRs open then you would like, looking at https://github.com/apache/flink/pulls :)
There have been discussions in the Flink community about forking Calcite [1]. My personal preference at the moment is to see if we can create a better collaboration and community. I believe that we can find people from the Flink community who can open / help reviewing Calcite PRs that are interesting for the Flink community. The question is if that will also help short term since in the end it still requires a Calcite maintainer to review/merge. Best regards, Martijn [1] https://lists.apache.org/thread/1oqydpsm4mc55bkk440gx9lr9gf2rvf4 Op ma 20 jun. 2022 om 23:51 schreef Austin Bennett < whatwouldausti...@gmail.com>: > From the peanut gallery :-) --> > > Wow; yes, lots of open PRs. https://github.com/apache/calcite/pulls > > How can individuals from the Flink [sub-]community, and/or more general > calcite community help lighten this load? Is there much weight given to > reviews from non-committers; how to increase the # of people capable of > providing worthwhile reviews [ that are recognized as such ]? > > > > On Mon, Jun 20, 2022 at 11:47 AM Julian Hyde <jhyde.apa...@gmail.com> > wrote: > > > Martijn, > > > > Since you requested a reply, I am replying. To answer your question, I > > don’t know of a way to move this topic forward. We have more PRs than > > people to review them. > > > > Julian > > > > > > > On Jun 19, 2022, at 11:58 PM, Martijn Visser <martijnvis...@apache.org > > > > wrote: > > > > > > Hi everyone, > > > > > > I just wanted to reach out to the Calcite community once more on this > > topic > > > since no reply was received. Would be great if someone could get back > to > > us. > > > > > > Best regards, > > > > > > Martijn > > > > > > Op wo 8 jun. 2022 om 11:24 schreef Martijn Visser < > > martijnvis...@apache.org > > >> : > > > > > >> Hi everyone, > > >> > > >> I would like to follow-up on this email that was sent by Jing. So far, > > no > > >> progress has been made, despite reaching out to the mailing list, the > > >> original Jira ticket and reaching out to people directly. Is there a > way > > >> that we can move this PR/topic forward? > > >> > > >> For context, in Apache Flink we're currently heavily using Calcite. > > >> However, we are now at the stage where Calcite is actually holding us > > back. > > >> It would be great if we can find a way to strengthen our bond and move > > both > > >> Calcite and Flink forward. > > >> > > >> Looking forward to your thoughts, > > >> > > >> Martijn > > >> > > >> On 2022/01/26 07:05:37 Jing Zhang wrote: > > >>> Hi community, > > >>> My apologies for interrupting. > > >>> Anyone could help to review the pr > > >>> https://github.com/apache/calcite/pull/2606? > > >>> Thanks a lot. > > >>> > > >>> CALCITE-4865 is the first sub-task of CALCITE-4864. This Jira aims to > > >>> extend existing Table function in order to support Polymorphic Table > > >>> Function which is introduced as the part of ANSI SQL 2016. > > >>> > > >>> The brief change logs of the PR are: > > >>> - Update `Parser.jj` to support partition by clause and order by > > clause > > >>> for input table with set semantics of PTF > > >>> - Introduce `TableCharacteristics` which contains three > > characteristics > > >>> of input table of table function > > >>> - Update `SqlTableFunction` to add a method `tableCharacteristics`, > > >> the > > >>> method returns the table characteristics for the ordinal-th argument > to > > >>> this table function. Default return value is Optional.empty which > means > > >> the > > >>> ordinal-th argument is not table. > > >>> - Introduce `SqlSetSemanticsTable` which represents input table with > > >> set > > >>> semantics of Table Function, its `SqlKind` is `SET_SEMANTICS_TABLE` > > >>> - Updates `SqlValidatorImpl` to validate only set semantic table of > > >> Table > > >>> Function could have partition by and order by clause > > >>> - Update `SqlToRelConverter#substituteSubQuery` to parse subQuery > > which > > >>> represents set semantics table. > > >>> > > >>> PR: https://github.com/apache/calcite/pull/2606 > > >>> JIRA: https://issues.apache.org/jira/browse/CALCITE-4865 > > >>> Parent JARA: https://issues.apache.org/jira/browse/CALCITE-4864 > > >>> > > >>> Best, > > >>> Jing Zhang > > >>> > > >> > > > > >
