Calcite-Master - Build # 1354 - Still Failing

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

Re: Integrating Calcite, Omid, Avatica, Avro, and Kafka

Personally, I think a separate section would be preferable although it could be formatted the same way as the news so it should be equally easy to maintain. I think separating it would be nice because it's not necessarily "news" and I don't think we want to suggest it's authoritative. -- Michael

Calcite-Master - Build # 1353 - Still Failing

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

[jira] [Created] (CALCITE-3370) Emulate NULL direction for MSSQL

Justin Swett created CALCITE-3370: - Summary: Emulate NULL direction for MSSQL Key: CALCITE-3370 URL: https://issues.apache.org/jira/browse/CALCITE-3370 Project: Calcite Issue Type: Task

[jira] [Created] (CALCITE-3369) In LatticeSuggester, recommend lattices based on UNION queries

Julian Hyde created CALCITE-3369: Summary: In LatticeSuggester, recommend lattices based on UNION queries Key: CALCITE-3369 URL: https://issues.apache.org/jira/browse/CALCITE-3369 Project: Calcite

Re: Integrating Calcite, Omid, Avatica, Avro, and Kafka

Hi, I agree with that and would love such a section (with timestamps). This could also make it easier for newcomers to learn about calcite. Julian From: Julian Hyde Sent: Tuesday, September 24, 2019 8:50:21 PM To: dev Subject: Re: Integrating Calcite, Omid,

Calcite-Master - Build # 1352 - Still Failing

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

Re: Integrating Calcite, Omid, Avatica, Avro, and Kafka

I like the idea of time-ordered articles. It creates less expectation the articles are “definitive”. How about using the “news” section of our site? [1] We use it mainly for releases, but it’s good for other news too (see the “Other news” section). Jekyll mades it pretty easy to add a news

Re: Trivial query simplification

A few thoughts on this. 0. I am surprised that this simplification does not happen, and I think we should do it. Specifically, "filter(x = 0 and x is not null)" should simplify to “filter(x = 0)”. 1. Enrico, please log a JIRA case now, and transcribe the key points of this discussion into

Re: Trivial query simplification

Il giorno mar 24 set 2019 alle ore 13:45 XING JIN ha scritto: > "v = 1 and v is null" > cannot be simplified to "v = 1" not matter v is nullable or not nullable > > If you really mean that "v is not null", I made below test case in > RelOptRulesTest.java for illustration: > > > // mgr is

Re: Integrating Calcite, Omid, Avatica, Avro, and Kafka

I agree that it will get out of date. But I think we would just put the date on each article we post and leave it to the reader to decide if what is posted is still relevant. We could perhaps include a disclaimer. I think it's useful for newcomers to see the activity happening around Calcite. --

Re: Trivial query simplification

"v = 1 and v is null" cannot be simplified to "v = 1" not matter v is nullable or not nullable If you really mean that "v is not null", I made below test case in RelOptRulesTest.java for illustration: // mgr is nullable @Test public void testDEV() throws Exception { HepProgram program =

Re: Trivial query simplification

Il mar 24 set 2019, 11:50 Feng Zhu ha scritto: > Hi, Enrico, > I'm a little confused about your expectations. Could you clarify it? > Moreover, is it right for the below simplification (do you mean v is not > null)? > (v=1 and v is null) -> v=1 > (do you mean v is not null?) > Yes, sorry

[jira] [Created] (CALCITE-3368) Nonequivalent simplification happens in RexSimplify

Leonard Xu created CALCITE-3368: --- Summary: Nonequivalent simplification happens in RexSimplify Key: CALCITE-3368 URL: https://issues.apache.org/jira/browse/CALCITE-3368 Project: Calcite Issue

Re: Trivial query simplification

Hi, Enrico, I'm a little confused about your expectations. Could you clarify it? Moreover, is it right for the below simplification (do you mean v is not null)? (v=1 and v is null) -> v=1 (do you mean v is not null?) Best regards Enrico Olivelli 于2019年9月24日周二 下午5:41写道： > Hi, > I have a query

Trivial query simplification

Hi, I have a query like SELECT * FROM MYTABLE WHERE v = 1 and v is null I am expecting Calcite to simplify it to SELECT * FROM MYTABLE WHERE v = 1 but this does not happen. Is any rule I should enable in order to make it happen ? This is the configuration of my Volcano planner: final

Calcite-Master - Build # 1351 - Failure

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