Re: Calcite travis jdk11 failed while compilation of calcite-elasticsearch2 on travis

I think this might actually be a JDK bug. Let's wait a bit for a new EA release. Mit freundlichen Grüßen, *Christian Beikov* Am 12.06.2018 um 22:14 schrieb Julian Hyde: What would be the command-line arguments to achieve

Re: Calcite travis jdk11 failed while compilation of calcite-elasticsearch2 on travis

PS Can someone please log a JIRA case for this. At the very least we need to modify HISTORY.md to say which ES versions are supported with each JDK. If we can make a code fix, even better. > On Jun 12, 2018, at 3:14 PM, Julian Hyde wrote: > > What would be the command-line arguments to

Re: Calcite travis jdk11 failed while compilation of calcite-elasticsearch2 on travis

What would be the command-line arguments to achieve this? I will add them to my nightly build scripts. I already skip certain Guava versions based on JDK. Julian > On Jun 12, 2018, at 12:42 PM, Kevin Risden wrote: > > We might want to skip JDK11 with ES 2.x. 2.x is EOL from Elastic. I can

Re: Calcite travis jdk11 failed while compilation of calcite-elasticsearch2 on travis

We might want to skip JDK11 with ES 2.x. 2.x is EOL from Elastic. I can look into this if it helps. Kevin Risden On Tue, Jun 12, 2018, 10:54 Christian Beikov wrote: > Seems the latest Java 11 build will be stricter about the manifest > format when reading. Also see other reports here: > > *

[jira] [Created] (CALCITE-2359) Inconsistent behavior when casting interval literals to integer

James Duong created CALCITE-2359: Summary: Inconsistent behavior when casting interval literals to integer Key: CALCITE-2359 URL: https://issues.apache.org/jira/browse/CALCITE-2359 Project: Calcite

Re: Calcite travis jdk11 failed while compilation of calcite-elasticsearch2 on travis

Seems the latest Java 11 build will be stricter about the manifest format when reading. Also see other reports here: * https://bugs.eclipse.org/bugs/show_bug.cgi?id=535774 * https://issues.jenkins-ci.org/browse/JENKINS-51871?workflowName=JNJira+%2B+In-Review=1 Not sure if there is anything

Calcite travis jdk11 failed while compilation of calcite-elasticsearch2 on travis

Hello everyone Just I have an issue related to compilation of calcite-elasticsearch2 on travis As I see it relates only jdk11 while with others compiles ok e.g. https://travis-ci.org/apache/calcite/builds/391198921 could anyone please share knowledge how to overcome this? -- Best regards,

Re: How to add user defined functions in schema

I assume you need to implement this method org.apache.calcite.schema.impl.AbstractSchema.getFunctionMultimap(). I'm not sure, I haven't got there yet. I appreciate if you share your experience with that. Thanks, Gelbana On Mon, Jun 11, 2018 at 8:54 AM, subbarao mitta wrote: > IAM already

[jira] [Created] (CALCITE-2358) Use null literal instead of empty string as argument for timestamp_parse Druid expression

slim bouguerra created CALCITE-2358: --- Summary: Use null literal instead of empty string as argument for timestamp_parse Druid expression Key: CALCITE-2358 URL: https://issues.apache.org/jira/browse/CALCITE-2358

Re: Oracle ROWNUM

Yes, that was hidden field, without validation failed. Should I add the rule? Or the transformation should happen during the SQL parsing? I see that MYSQL lex create SqlOrderBy class with fetch. I want the SQL parser to recognize limits. Like it works for MYSQL. But from the other hand, this

Calcite-Master - Build # 298 - Still Failing

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