Calcite-Master - Build # 320 - Still Failing

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

Re: [DISCUSS] Towards Calcite 1.17.0

2018-07-02 Thread Volodymyr Vysotskyi
I think I can finish CALCITE-2392 on Wed or Thursday. Kind regards, Volodymyr Vysotskyi пн, 2 лип. 2018 о 21:22 Julian Hyde пише: > OK, so 2384 and 2392 are the critical path. > > Zoltan, when do you think you can finish 2392? > > Volodymr, when do you think you can finish 2384? > > When we

Re: [DISCUSS] Towards Calcite 1.17.0

2018-07-02 Thread Julian Hyde
OK, so 2384 and 2392 are the critical path. Zoltan, when do you think you can finish 2392? Volodymr, when do you think you can finish 2384? When we have these answers we can set a target date for the RC. Julian > On Jul 2, 2018, at 11:13 AM, Volodymyr Vysotskyi wrote: > > Hi, > > Here is

Re: [DISCUSS] Towards Calcite 1.17.0

2018-07-02 Thread Volodymyr Vysotskyi
Hi, Here is the list of the Jiras, which in my opinions should be fixed before the release: - https://issues.apache.org/jira/browse/CALCITE-2384 Performance issue - https://issues.apache.org/jira/browse/CALCITE-2392 Regression appeared after 1.16 (not sure about blocker status for this Jira) -

Calcite-Master - Build # 319 - Still Failing

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

Re: [DISCUSS] Towards Calcite 1.17.0

2018-07-02 Thread Julian Hyde
> On Jun 29, 2018, at 7:29 PM, Francis Chuang wrote: > > Can someone please confirm that the following PRs can be closed? > https://github.com/apache/calcite/pull/180 > > https://github.com/apache/calcite/pull/17 >

Re: [DISCUSS] Towards Calcite 1.17.0

2018-07-02 Thread Michael Mior
I asked INFRA and they can only close issues on request. They can't grant permissions. -- Michael Mior mm...@apache.org Le lun. 2 juil. 2018 à 08:17, Enrico Olivelli a écrit : > Il giorno lun 2 lug 2018 alle ore 14:12 Michael Mior ha > scritto: > > > It's not really that I think closing

[jira] [Created] (CALCITE-2394) Avatica applies calendar offset to timestamps when they should remain unchanged

2018-07-02 Thread Kenneth Knowles (JIRA)
Kenneth Knowles created CALCITE-2394: Summary: Avatica applies calendar offset to timestamps when they should remain unchanged Key: CALCITE-2394 URL: https://issues.apache.org/jira/browse/CALCITE-2394

[jira] [Created] (CALCITE-2393) RexSimplify optimization error for expression 'x is not null and x <> 5'

2018-07-02 Thread pengzhiwei (JIRA)
pengzhiwei created CALCITE-2393: --- Summary: RexSimplify optimization error for expression 'x is not null and x <> 5' Key: CALCITE-2393 URL: https://issues.apache.org/jira/browse/CALCITE-2393 Project:

Re: [DISCUSS] Towards Calcite 1.17.0

2018-07-02 Thread Michael Mior
It's not really that I think closing stale PRs warrants an entry in the commit log, it's that I don't like the idea of polluting other commits. But it's not really that big of a deal so if others prefer that route, fine by me. As far as Enrico's suggestion, I've always had my Apache ID associated

Re: [DISCUSS] Towards Calcite 1.17.0

2018-07-02 Thread Enrico Olivelli
Il lun 2 lug 2018, 06:33 Julian Hyde ha scritto: > I disagree with Michael. Closing rejected PRs is not important enough to > warrant making an entry in the commit log. > I agree with Julian > Regarding Enrico’s comments. I would be nice if there was a way for > committers to close PRs, and