removing "metadata" schema

Hello, I have an inline model text. All entries are of custom type. Is there a way abandon creation of the "metadata" schema? (In my case it's empty.) Thank you, - Alexey.

[jira] [Created] (CALCITE-2064) Allow a Convention to declare which sub-classes of RelNode it handles

Julian Hyde created CALCITE-2064: Summary: Allow a Convention to declare which sub-classes of RelNode it handles Key: CALCITE-2064 URL: https://issues.apache.org/jira/browse/CALCITE-2064 Project:

[jira] [Created] (CALCITE-2063) Add JDK 10 to CI

Julian Hyde created CALCITE-2063: Summary: Add JDK 10 to CI Key: CALCITE-2063 URL: https://issues.apache.org/jira/browse/CALCITE-2063 Project: Calcite Issue Type: Bug Reporter:

Calcite-Master - Build # 151 - Still Failing

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

Calcite-Master - Build # 150 - Still Failing

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

Calcite-Master - Build # 149 - Still Failing

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

[jira] [Created] (CALCITE-2062) Prevent creating an Aggregate with grouping columns that are not present in grouping sets

Jesus Camacho Rodriguez created CALCITE-2062: Summary: Prevent creating an Aggregate with grouping columns that are not present in grouping sets Key: CALCITE-2062 URL:

Re: why does SemiJoin only support equi join condition in Calcite ?

You are talking about what I would call “theta semi-join” (as opposed to the “equi-semi-join” that we support currently). But you are correct; there is no reason in principle why the predicate has to be “=“. IN translates naturally to an equi-SemiJoin; your query "select * from l where l.a in

Re: Another error on using unbounded dynamic parameters

See my comment https://issues.apache.org/jira/browse/CALCITE-2054?focusedCommentId=16259687=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16259687

Re: Connection time zone concept

I don’t know the answer but I would start off with a solid set of data types, each with obvious semantics and defined by a standard: * An instant (per Joda) represents a moment in time (you can think of it as an offset from UTC epoch). Adding a day to an instant is the same as adding 24 hours.

Connection time zone concept

Hi Calcites, In Druid SQL we have a connection time zone concept; see the mentions of "sqlTimeZone" here: http://druid.io/docs/latest/querying/sql.html. It affects the time zone of any operation involving timestamps, including the interpretation of literals, the behavior of functions like FLOOR

Re: Support for "limit ?"

I have a proble on JdbcTest, I can't find how to test dynamic parameters. Can you give some hint ? A part from this a will send my patch soon Enrico 2017-11-17 19:41 GMT+01:00 Enrico Olivelli : > > > Il ven 17 nov 2017, 19:29 Julian Hyde ha scritto: > >>

Avatica documentation update

I'm much less familiar with Avatica than I am the rest of Calcite, but I was browsing through the documentation and it looks like it could use an update. https://calcite.apache.org/avatica/docs/ * Avatica is (somewhat) a separate project now * The Avatica Go driver has moved locations If