Calcite-Master - Build # 250 - Still Failing

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

Calcite-Avatica-Master - Build # 49 - Failure

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

Calcite-Master - Build # 249 - Failure

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

[jira] [Created] (CALCITE-2248) Take advantage of Calcite DDL

Andrew Pilloud created CALCITE-2248: --- Summary: Take advantage of Calcite DDL Key: CALCITE-2248 URL: https://issues.apache.org/jira/browse/CALCITE-2248 Project: Calcite Issue Type: New

Re: JDK 8 syntax

I’d really appreciate that. Can you please log a JIRA case, and record your observations/progress there. There’s no particular hurry on this one. Julian > On Apr 10, 2018, at 06:32, Enrico Olivelli wrote: > > 2018-04-10 13:48 GMT+02:00 Julian Hyde

Re: JDK 8 syntax

2018-04-10 13:48 GMT+02:00 Julian Hyde : > Yes, that’s it. > > Next step would be to check whether the generated code is the same as > previously, and if so, it is a Janino bug. Then try to create a minimal > test case for Janino. Maybe we can work around by adding an

Re: JDK 8 syntax

This is "the" error (see below). Unfortunately just be upgrading Janino to 3.0.8 the problem still is present. the only 'unwrap' word in the generated code is here ... public org.apache.calcite.linq4j.Enumerable bind(final org.apache.calcite.DataContext root0) { root = root0; final

[jira] [Created] (CALCITE-2246) column alias in view will cause duplicate column exception

Yongqian Wang created CALCITE-2246: -- Summary: column alias in view will cause duplicate column exception Key: CALCITE-2246 URL: https://issues.apache.org/jira/browse/CALCITE-2246 Project: Calcite

Re: Use of CalciteSchema across Calcite

Sorry, I misinterpreted your last message. As for Dremio/Drill, the model offered by CalciteSchema is not scalable as it requires all subschemas and tables to be loaded, even if only one table is accessed: fetching all metadata might be an expensive operation depending on the type and number of

Re: Use of CalciteSchema across Calcite

That was my understanding, but it seems usage of CalciteSchema is prevalent outside the scope of the JDBC adapter: $ grep -rl import.*CalciteSchema core/src/main/java|grep -v calcite/jdbc core/src/main/java/org/apache/calcite/materialize/Lattice.java