That’s great. Now Kylin is up to speed, and because Calcite releases about once per month, when you log an issue such as https://issues.apache.org/jira/browse/CALCITE-788 we can get the issue fixed in Calcite, released in Calcite, and into a released version of Kylin within a couple of months.
On Jul 7, 2015, at 1:38 AM, Li Yang <[email protected]> wrote: > Yeah, upgraded to 1.3.0 on branch 0.7-staging & 0.8. The calcite-core API > change is minimal, while avacita API upgrade took me some time. > > Kylin shall keep up with latest calcite release from now on. :-) > > On Tue, Jul 7, 2015 at 10:17 AM, Li Yang <[email protected]> wrote: > >>> Upgrading to 1.3 should give you a lot of benefit for modest investment >> >> Sounds charming~~ Let me have a quick try. :-) >> >> On Tue, Jul 7, 2015 at 4:18 AM, Julian Hyde <[email protected]> wrote: >> >>> Great news, and well done! >>> >>> Getting to 1.0 was the hard part, because of the API changes, but I >>> suggest you don’t stop there. >>> >>> Calcite has continued to evolve over the last 6 months (see release notes >>> [1]); 1.3 is the latest release and 1.4 is probably a couple of weeks away. >>> There are a lot of improvements and bug-fixes in each release, and since >>> these are minor releases post 1.0, we have made efforts to maintain >>> compatibility. >>> >>> Upgrading to 1.3 should give you a lot of benefit for modest investment, >>> so I think you should do it as soon as possible. I’ll be glad to help. >>> >>> Julian >>> >>> [1] http://calcite.incubator.apache.org/docs/history.html >>> >>> >>> >>> On Jul 5, 2015, at 11:16 PM, Li Yang <[email protected]> wrote: >>> >>>> KYLIN-780 is finally resolved. The latest branch of 0.7 & 0.8 now uses >>>> Calcite 1.0. >>>> >>>> This means Kylin's SQL capability has stepped up to a higher level. E.g. >>>> the support of window function should be very close. (It maybe already >>>> supported, I just haven't tested yet.) >>>> >>>> >>>> Cheers >>>> Yang >>> >>> >>
