[jira] [Commented] (CALCITE-2059) Apache Geode adapter
[ https://issues.apache.org/jira/browse/CALCITE-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361825#comment-16361825 ] Julian Hyde commented on CALCITE-2059: -- Regarding REGION_MAP and JAVA_TYPE_FACTORY - let's re-visit later. I would like to get this committed (and I'm sure you would, too). If you address my comments for GeodeAggregationSort and Main1Foo we're good to go. > Apache Geode adapter > > > Key: CALCITE-2059 > URL: https://issues.apache.org/jira/browse/CALCITE-2059 > Project: Calcite > Issue Type: New Feature > Components: geode >Reporter: Christian Tzolov >Assignee: Julian Hyde >Priority: Major > > I've been working on a Calcite adapter for [Apache > Geode|http://geode.apache.org]. > Current implementation uses the plain Geode API and > [OQL|http://geode.apache.org/docs/guide/13/developing/querying_basics/chapter_overview.html](Object > Query Interface) to push down relational expressions such as projections, > filtering, sorting, and grouping . > Provided functionality can hopefully address certain Geode use cases and will > provide a stepping stone for future improvements. > Here are some remaining tasks as i see it: > * New tests for test suite (and update calcite-test-dataset to support Geode) > * Add Integration tests that use calcite-test-dataset > * Documentation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-2128) Add jethro sql dialect and jdbc support
[ https://issues.apache.org/jira/browse/CALCITE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361806#comment-16361806 ] Julian Hyde commented on CALCITE-2128: -- [~msydoron], In [9468640d0f62fbaafde1e615fc639cfb74cd3137|https://github.com/julianhyde/calcite/commit/9468640d0f62fbaafde1e615fc639cfb74cd3137] I made a few changes, such as renaming JethrodataSqlDialect to JethroDataSqlDialect, and removing 'throws SQLException' from SqlDialectFactory.create. Then I rebased and squashed, to create [julianhyde/master|https://github.com/julianhyde/calcite/commit/da1ba5d8cf056a73cffac30435b5e19afb9ad47f]. Please review, and I will push to master. > Add jethro sql dialect and jdbc support > --- > > Key: CALCITE-2128 > URL: https://issues.apache.org/jira/browse/CALCITE-2128 > Project: Calcite > Issue Type: Improvement > Components: jdbc-adapter >Reporter: Jonathan Doron >Assignee: Jonathan Doron >Priority: Major > Fix For: 1.16.0 > > > Calcite Jdbc operators code needs to be public so it could be used in hive > code to support usage of external jdbc tables in hive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (CALCITE-1561) Intermittent test failures
[
https://issues.apache.org/jira/browse/CALCITE-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-1561:
-
Comment: was deleted
(was: 8. ConcurrentModificationException in BlockBuilder.optimize called from
misc.iq
{noformat}java.lang.AssertionError: Files differ:
/Users/jhyde/open1/calcite.1/core/target/surefire/sql/misc.iq
/Users/jhyde/open1/calcite.1/core/target/test-classes/sql/misc.iq
626,633c626,699
< ++
< | P |
< ++
< | {0, 12}|
< | {null, 12} |
< ++
< (2 rows)
<
---
> java.sql.SQLException: Error while executing SQL "select period("sqlDate",
> INTERVAL '1' YEAR) as p
> from "everyTypes"
> ": null
> at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
> at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:156)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeQuery(AvaticaStatement.java:218)
> at
> net.hydromatic.quidem.Quidem$CheckResultCommand.execute(Quidem.java:830)
> at
> net.hydromatic.quidem.Quidem$CompositeCommand.execute(Quidem.java:1450)
> at net.hydromatic.quidem.Quidem.execute(Quidem.java:197)
> at org.apache.calcite.test.QuidemTest.checkRun(QuidemTest.java:152)
> at
> org.apache.calcite.test.CoreQuidemTest.testSqlMisc(CoreQuidemTest.java:67)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.apache.calcite.test.QuidemTest.test(QuidemTest.java:207)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> Caused by: java.util.ConcurrentModificationException
> at
[jira] [Commented] (CALCITE-1561) Intermittent test failures
[
https://issues.apache.org/jira/browse/CALCITE-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361764#comment-16361764
]
Julian Hyde commented on CALCITE-1561:
--
8. ConcurrentModificationException in BlockBuilder.optimize called from misc.iq
{noformat}java.lang.AssertionError: Files differ:
/Users/jhyde/open1/calcite.1/core/target/surefire/sql/misc.iq
/Users/jhyde/open1/calcite.1/core/target/test-classes/sql/misc.iq
626,633c626,699
< ++
< | P |
< ++
< | {0, 12}|
< | {null, 12} |
< ++
< (2 rows)
<
---
> java.sql.SQLException: Error while executing SQL "select period("sqlDate",
> INTERVAL '1' YEAR) as p
> from "everyTypes"
> ": null
> at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
> at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:156)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeQuery(AvaticaStatement.java:218)
> at
> net.hydromatic.quidem.Quidem$CheckResultCommand.execute(Quidem.java:830)
> at
> net.hydromatic.quidem.Quidem$CompositeCommand.execute(Quidem.java:1450)
> at net.hydromatic.quidem.Quidem.execute(Quidem.java:197)
> at org.apache.calcite.test.QuidemTest.checkRun(QuidemTest.java:152)
> at
> org.apache.calcite.test.CoreQuidemTest.testSqlMisc(CoreQuidemTest.java:67)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.apache.calcite.test.QuidemTest.test(QuidemTest.java:207)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> Caused by: java.util.ConcurrentModificationException
>
[jira] [Commented] (CALCITE-1406) Enable OLAP extensions
[ https://issues.apache.org/jira/browse/CALCITE-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361664#comment-16361664 ] zhen wang commented on CALCITE-1406: I am looking at JIRAs from time to time and sure to lend a hand if I can. are those Jiras under some umbrella, or they are just under CALCITE ? > Enable OLAP extensions > -- > > Key: CALCITE-1406 > URL: https://issues.apache.org/jira/browse/CALCITE-1406 > Project: Calcite > Issue Type: Bug >Reporter: Julian Hyde >Assignee: Julian Hyde >Priority: Major > > Allow extension projects to add OLAP statements to JDBC, and OLAP metadata > (cubes, dimensions) to the catalog. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-2046) Support "CREATE FUNCTION" DDL
[
https://issues.apache.org/jira/browse/CALCITE-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361279#comment-16361279
]
Julian Hyde commented on CALCITE-2046:
--
Yes, at some point. I think that two cases are higher priority: (1) loading all
functions from an external library (self-describing, so we don't need DDL for
each individual function), (2) CREATE FUNCTION with SQL as the language (since
it's SQL it can just be inlined into the query). But I wouldn't turn down a
pull request for "CREATE FUNCTION ... AS LANGUAGE ..."!
> Support "CREATE FUNCTION" DDL
> -
>
> Key: CALCITE-2046
> URL: https://issues.apache.org/jira/browse/CALCITE-2046
> Project: Calcite
> Issue Type: New Feature
>Reporter: Shuyi Chen
>Assignee: Shuyi Chen
>Priority: Major
>
> We want to add DDL support for creating external function like Apache Drill
> ([https://drill.apache.org/docs/create-function-using-jar/]).
> {code:java}
> CREATE FUNCTION USING JAR '.jar';
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CALCITE-1406) Enable OLAP extensions
[ https://issues.apache.org/jira/browse/CALCITE-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361240#comment-16361240 ] Julian Hyde commented on CALCITE-1406: -- Well, yes, but only if those PRs get finished. I'd welcome some help! > Enable OLAP extensions > -- > > Key: CALCITE-1406 > URL: https://issues.apache.org/jira/browse/CALCITE-1406 > Project: Calcite > Issue Type: Bug >Reporter: Julian Hyde >Assignee: Julian Hyde >Priority: Major > > Allow extension projects to add OLAP statements to JDBC, and OLAP metadata > (cubes, dimensions) to the catalog. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CALCITE-2175) Revisit the assumption made by druid calcite adapter that there is only one timestamp column
slim bouguerra created CALCITE-2175:
---
Summary: Revisit the assumption made by druid calcite adapter that
there is only one timestamp column
Key: CALCITE-2175
URL: https://issues.apache.org/jira/browse/CALCITE-2175
Project: Calcite
Issue Type: Task
Components: druid
Reporter: slim bouguerra
Assignee: Julian Hyde
Currently, the Druid Calcite adapter assumes that the row returned by druid has
only one timestamp typed column, this is not true, in fact, we can have
multiple projections of the time column with extraction functions. Thus code
like this need to be revisited.
{code}
int posTimestampField = -1;
for (int i = 0; i < fieldTypes.size(); i++) {
if (fieldTypes.get(i) == ColumnMetaData.Rep.JAVA_SQL_TIMESTAMP) {
posTimestampField = i;
break;
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CALCITE-1406) Enable OLAP extensions
[ https://issues.apache.org/jira/browse/CALCITE-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360600#comment-16360600 ] zhen wang commented on CALCITE-1406: MDX, finally MDX is coming to calcite > Enable OLAP extensions > -- > > Key: CALCITE-1406 > URL: https://issues.apache.org/jira/browse/CALCITE-1406 > Project: Calcite > Issue Type: Bug >Reporter: Julian Hyde >Assignee: Julian Hyde >Priority: Major > > Allow extension projects to add OLAP statements to JDBC, and OLAP metadata > (cubes, dimensions) to the catalog. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-2099) generated code compile error when sql has union and aggregation
[
https://issues.apache.org/jira/browse/CALCITE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360592#comment-16360592
]
zhen wang commented on CALCITE-2099:
https://github.com/apache/calcite/pull/625 created.
[~julianhyde] let me know your comments
> generated code compile error when sql has union and aggregation
> ---
>
> Key: CALCITE-2099
> URL: https://issues.apache.org/jira/browse/CALCITE-2099
> Project: Calcite
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: jiatao.tao
>Assignee: Julian Hyde
>Priority: Major
>
> Hi, [~julianhyde], add these tests in CsvTest
> {code:java}
> // fail
> @Test
> public void test0() throws SQLException {
> sql("model", "select count(*) from EMPS group by NAME union select
> count(*) from EMPS group by NAME").ok();
> }
> // fail
> @Test
> public void test1() throws SQLException {
> sql("model", "select sum(AGE) from EMPS group by NAME union select
> sum(AGE) from EMPS group by NAME").ok();
> }
> // this is ok
> @Test
> public void test2() throws SQLException {
> sql("model", "select count(*), NAME from EMPS group by NAME union
> select count(*), NAME from EMPS group by NAME").ok();
> }
> {code}
> and will throw exception:Caused by:
> org.codehaus.commons.compiler.CompileException: Line 202, Column 17: No
> applicable constructor/method found for actual parameters "java.lang.String,
> java.lang.Integer"; candidates are: "Baz$Record2_1()"
> Hoping for your reply.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
