I don’t feel strongly about it, but my vote is for 1.15 rather than 1.14.1.
I don’t want people to infer that it’s easy for us to do patch releases and start requesting them on a whim. (It’s not that hard, but we’re all volunteers.) Julian > On Apr 30, 2019, at 4:16 PM, Francis Chuang <[email protected]> wrote: > > I am happy to be RM for the next version of Avatica. This should be a pretty > small release with 1 bug fix. > > Before I open a separate thread for it, should it be 1.14.1 or 1.15.0? We > have never made patch releases and have always made minor or major releases. > > On 1/05/2019 9:12 am, Kai Jiang wrote: >> +1 release 1.14.1 or 1.15.0 for unblocking CALCITE-3040 >> On Tue, Apr 30, 2019 at 3:59 PM Julian Hyde <[email protected]> wrote: >>> I think that CALCITE-3040 means that Avatica 1.14.0 is not a useful >>> release. (I do take Vladimir’s point that clients should be smarter. But >>> they are not. We changed, and we broke them.) So let’s release an Avatica >>> 1.14.1 or 1.15 before we release Calcite 1.20. >>> >>>> On Apr 30, 2019, at 3:20 PM, Francis Chuang <[email protected]> >>> wrote: >>>> >>>> Since Avatica 1.14.0 is now release, I think the Avatica dependency can >>> also be upgraded. However, CALCITE-3040 [1] was just opened for Avatica and >>> appears to be caused by CALCITE-2845 [2]. If this is a blocker for Calcite, >>> we can (maybe) wait until Avatica 1.15.0 is released and upgrade it in the >>> next Calcite release, but I do think the Jetty upgrade to Avatica 1.14.0 is >>> a pretty important. >>>> >>>> Francis >>>> >>>> [1] https://issues.apache.org/jira/browse/CALCITE-3040 >>>> [2] https://issues.apache.org/jira/browse/CALCITE-2845 >>>> >>>> On 1/05/2019 2:32 am, Lai Zhou wrote: >>>>> how about these: >>>>> [CALCITE-2973] Allow theta joins that have equi conditions to be >>> executed >>>>> using a hash join algorithm >>>>> [CALCITE-2282] Allow OperatorTable to be pluggable in the parser >>>>> [CALCITE-2992] Enhance implicit conversions when generating hash join >>> keys >>>>> for an equi condition >>>>> Julian Hyde <[email protected]> 于2019年5月1日周三 上午12:13写道： >>>>>> Let’s get >>>>>> >>>>>> [CALCITE-2969] Improve design of join-like relational expressions >>>>>> >>>>>> into the release. We are renaming a few classes and interfaces, so we >>> will >>>>>> probably want to keep the old ones around, deprecated, in 1.20, and >>> remove >>>>>> them in 1.21. The sooner we start that process the sooner we finish. >>>>>> >>>>>> Julian >>>>>> >>>>>> >>>>>>> On Apr 30, 2019, at 8:47 AM, Ruben Q L <[email protected]> wrote: >>>>>>> >>>>>>> Thanks for starting this discussion, Michael. >>>>>>> >>>>>>> I would also add to the list (even though it will be flagged as >>>>>>> "experimental"): >>>>>>> CALCITE-2812 Add algebraic operators to allow expressing recursive >>>>>>> queries >>>>>>> >>>>>>> Best regards, >>>>>>> Ruben >>>>>>> >>>>>>> >>>>>>> Le mar. 30 avr. 2019 à 17:15, Michael Mior <[email protected]> a >>> écrit : >>>>>>> >>>>>>>> Calcite 1.19.0 was released approximately one month ago. This was >>>>>>>> later than we originally planned (although I think with good reason >>>>>>>> and I'm happy with what made it into this release). I don't think >>>>>>>> there's an imminent need for a new release, but I wanted to start the >>>>>>>> discussion now that Avatica has had it's latest release. >>>>>>>> >>>>>>>> There's a few big things in progress below that I thought I'd see if >>>>>>>> we want to try to include in the next release. Apologies if I missed >>>>>>>> any. >>>>>>>> >>>>>>>> CALCITE-1581 UDTF like in hive >>>>>>>> CALCITE-2952 Certify Calcite on JDK 12 >>>>>>>> CALCITE-3036 Remove correlate variables from Join >>>>>>>> CALCITE-3037 Rename EnumerableThetaJoin to EnumerableNestedLoopJoin >>>>>>>> >>>>>>>> -- >>>>>>>> Michael Mior >>>>>>>> [email protected] >>>>>>>> >>>>>> >>>>>> >>> >>>
