Re: Not able use PostgresDialect.

Thanks @Danny Chan , Please tell me one more thing: Just curious what does the PostgresSqlDialect accomplish in Calcite, if not to parse postgres sqls? *Shivraj Singh* Software Consultant Knoldus Inc. +91-8800782123 Canada - USA - India - Singapore

Re: [ DISCUSS ] Revert change: CALCITE-3713 Remove column names from Project#digest

> if you use explain_digest attributes, it means you expect it might change due to implementation details. That is what you just defined that, why a digest should be changed just because of the implementation. Best, Danny Chan 在 2020年2月14日 +0800 PM2:54，Vladimir Sitnikov ，写道： > The subject of

Re: Not able use PostgresDialect.

You should extend the babel parser by yourself. Shivraj Singh 于2020年2月14日 周五下午2:33写道： > I tried for BABEL conformance but it also doesn't work. > This is the way I used it: > > val sqlParserConfig = SqlParser.configBuilder() > .setParserFactory(SqlParserImpl.FACTORY) >

Re: [ DISCUSS ] Revert change: CALCITE-3713 Remove column names from Project#digest

The subject of the mail does not match the body. Please double check and ensure you mention a single change. PS if you use explain_digest attributes, it means you expect it might change due to implementation details. Vladimir

Re: Not able use PostgresDialect.

I tried for BABEL conformance but it also doesn't work. This is the way I used it: val sqlParserConfig = SqlParser.configBuilder() .setParserFactory(SqlParserImpl.FACTORY) .setConformance(SqlConformanceEnum.BABEL) .setConfig(sqlParserA) .build()

[ DISCUSS ] Revert change: CALCITE-3713 Remove column names from Project#digest

The change in CALCITE-3713 make a radical change to the plan digest, but it only brings in little promotion(at least from Calcite tests and Flink cases) During the upgrade of Flink Calcite version to 1.22.0-SNAPSHOT, the 2000+ plan changes to due to this patch, it is hard for me to figure out

[jira] [Created] (CALCITE-3796) Support Array operator <, <=, >, >=

Rui Wang created CALCITE-3796: - Summary: Support Array operator <, <=, >, >= Key: CALCITE-3796 URL: https://issues.apache.org/jira/browse/CALCITE-3796 Project: Calcite Issue Type: Improvement

Calcite-Master - Build # 1607 - Failure

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

Build failed in Jenkins: Calcite-Snapshots #113

See Changes: [rubenql] [CALCITE-3783] PruneEmptyRules#JOIN_RIGHT_INSTANCE wrong behavior for [h.yuan] [CALCITE-3785] HepPlanner.belongToDag() doesn't have to use [jhyde] Add RelBuilder.transform, which allows

Calcite-Master - Build # 1605 - Still Failing

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

Re: RelNode rewrite

Hey Christian, On Thu, Feb 13, 2020 at 6:30 PM Christian Beikov wrote: > Hello, > > I'm trying to generate SQL for a trigger that requires a little rewrite > of a RelNode structure and I wanted to know if anyone could help me > figure out how to do a few things > > * I need to swap left and

RelNode rewrite

Hello, I'm trying to generate SQL for a trigger that requires a little rewrite of a RelNode structure and I wanted to know if anyone could help me figure out how to do a few things * I need to swap left and right of a LogicalJoin. Doing that messes up predicates and projections though.

Re: Not able use PostgresDialect.

Note that Calcite's default parser only parses SQL in Calcite's dialect (with a little leeway such as choice of quoting characters). To parse other dialects, use the Babel parser. It can handle (or could handle) SQL extensions that are not in standard SQL and which we don't want to bring into

Re: Not able use PostgresDialect.

If you want to parse the sql in PostgreSQL dialect, there is no way to do that now. You need a new SqlConformance actually. Shivraj Singh 于2020年2月13日 周四下午3:50写道： > Hi, I want to parse the query of PostgreSQL via Calcite and while I am > parsing the query using the calcite parser it gives me

[jira] [Created] (CALCITE-3795) Promote the Project digest to only print "0" instead of "0..0" when there is only one trivial field

Danny Chen created CALCITE-3795: --- Summary: Promote the Project digest to only print "0" instead of "0..0" when there is only one trivial field Key: CALCITE-3795 URL:

[jira] [Created] (CALCITE-3794) Return directly if there is no pulled up predicate

Chunwei Lei created CALCITE-3794: Summary: Return directly if there is no pulled up predicate Key: CALCITE-3794 URL: https://issues.apache.org/jira/browse/CALCITE-3794 Project: Calcite Issue