[jira] [Created] (CALCITE-4120) Inconsistent Calendar used In JdbcMeta between prepareAndExecute and Fetch

Chris Snowden created CALCITE-4120: -- Summary: Inconsistent Calendar used In JdbcMeta between prepareAndExecute and Fetch Key: CALCITE-4120 URL: https://issues.apache.org/jira/browse/CALCITE-4120 Proj

[jira] [Created] (CALCITE-4121) Avatica misplaces properties from URL while connecting

Gian Merlino created CALCITE-4121: - Summary: Avatica misplaces properties from URL while connecting Key: CALCITE-4121 URL: https://issues.apache.org/jira/browse/CALCITE-4121 Project: Calcite

[jira] [Created] (CALCITE-4122) Support on-demand rule matching

Haisheng Yuan created CALCITE-4122: -- Summary: Support on-demand rule matching Key: CALCITE-4122 URL: https://issues.apache.org/jira/browse/CALCITE-4122 Project: Calcite Issue Type: Improvem

[RESULT] [VOTE] Release apache-calcite-avatica-go-5.0.0 (release candidate 0)

Thanks to everyone who has tested the release candidate and given their comments and votes. The tally is as follows. 3 binding +1s: Danny Chan Francis Chuang Stamatis Zampetakis No 0s or -1s. Therefore, I am delighted to announce that the proposal to release Apache Calcite Avatica Go 5.0.0 h

Calcite-Master - Build # 1833 - Failure

The Apache Jenkins build system has built Calcite-Master (build #1833) Status: Failure Check console output at https://builds.apache.org/job/Calcite-Master/1833/ to view the results.

Re: [RESULT] [VOTE] Release apache-calcite-avatica-go-5.0.0 (release candidate 0)

Thanks for the great work, Francis ~ Best, Danny Chan 在 2020年7月15日 +0800 AM7:23，dev@calcite.apache.org，写道： > > Francis

Calcite and Enum Type

Hi, I am using Beam SQL which uses calcite. IN Beam we have logical types which we can use for Enumeration. But looks like they did not implement enumeration support for calcite. I want to give that support. But I could not find the right way to implement it. In my Enumeration is a HashMap. My que

Re: [DISCUSS] Default disable the RexNode normalization(or operands reorder)

+1 to move rex node normalization out of constructor. On a second thought, I can't help thinking, do we really need RexNode normalization? There are 2 kinds of normalization in current codebase: 1. reverse the operator $2 > $1 is reordered to $1 < $2, so that predicate a > b and b < a can be r

Re: [DISCUSS] Towards Calcite 1.24.0

Thank you for all your effort. Now there're only two issues(CALCITE-4000[1] and CALCITE-4118[2]) to be fixed in 1.24.0. As for CALCITE-4000, it needs a final review. Could you someone help review? As for CALCITE-4118, I could not find the PR for it. Could someone some point it out if I missed it?

Calcite-Master - Build # 1834 - Still Failing

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

Re: [DISCUSS] Default disable the RexNode normalization(or operands reorder)

I have extended the logic to support all the symmetrical operators(=, <> ..) and the binary comparison operators (>=, < ..), not only just RexInputRef. Customized sql operator can also benefit. [1] The way is to compare the operands with SqlKind first then fallback to their hashcode (eargely com