[jira] [Commented] (CALCITE-4136) ReduceExpressionsRule.FILTER_INSTANCE cannot be initialized by some JVM

[ https://issues.apache.org/jira/browse/CALCITE-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17162702#comment-17162702 ] Enrico Olivelli commented on CALCITE-4136: --   [https://adoptopenjdk.net/] {code:java} mvn -v

[jira] [Commented] (CALCITE-4136) ReduceExpressionsRule.FILTER_INSTANCE cannot be initialized by some JVM

[ https://issues.apache.org/jira/browse/CALCITE-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17162657#comment-17162657 ] Enrico Olivelli commented on CALCITE-4136: -- The second stacktrace is on HerdDB 0.18.0

[jira] [Commented] (CALCITE-2395) Support SELECT xxx FROM TABLE FOR UPDATE syntax

[ https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146049#comment-17146049 ] Enrico Olivelli commented on CALCITE-2395: -- I have got another request for this feature

[jira] [Commented] (CALCITE-3997) Problem with MERGE JOIN: java.lang.AssertionError: cannot merge join: left input is not sorted on left keys

[ https://issues.apache.org/jira/browse/CALCITE-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108053#comment-17108053 ] Enrico Olivelli commented on CALCITE-3997: -- [~hyuan] I confirm that on current master in

[jira] [Commented] (CALCITE-3997) Problem with MERGE JOIN: java.lang.AssertionError: cannot merge join: left input is not sorted on left keys

[ https://issues.apache.org/jira/browse/CALCITE-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107610#comment-17107610 ] Enrico Olivelli commented on CALCITE-3997: -- Thank you. I will check tomorrow if this patch

[jira] [Commented] (CALCITE-3997) Problem with MERGE JOIN: java.lang.AssertionError: cannot merge join: left input is not sorted on left keys

[ https://issues.apache.org/jira/browse/CALCITE-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107260#comment-17107260 ] Enrico Olivelli commented on CALCITE-3997: -- [~hyuan] I have removed that rules

[jira] [Comment Edited] (CALCITE-3997) Problem with MERGE JOIN: java.lang.AssertionError: cannot merge join: left input is not sorted on left keys

[ https://issues.apache.org/jira/browse/CALCITE-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107260#comment-17107260 ] Enrico Olivelli edited comment on CALCITE-3997 at 5/14/20, 12:34 PM:

[jira] [Resolved] (CALCITE-3998) Bad datatype for sum(n), it should be BIGINT but it is sometimes INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli resolved CALCITE-3998. -- Resolution: Not A Problem > Bad datatype for sum(n), it should be BIGINT but it is

[jira] [Commented] (CALCITE-3998) Bad datatype for sum(n), it should be BIGINT but it is sometimes INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107254#comment-17107254 ] Enrico Olivelli commented on CALCITE-3998: -- In this case Calcite looks very smart ! As K1 is

[jira] [Commented] (CALCITE-3998) Bad datatype for sum(n), it should be BIGINT but it is sometimes INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107167#comment-17107167 ] Enrico Olivelli commented on CALCITE-3998: -- [~winipanda] I have run the tests adding

[jira] [Commented] (CALCITE-3998) Bad datatype for sum(n), it should be BIGINT but it is sometimes INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107159#comment-17107159 ] Enrico Olivelli commented on CALCITE-3998: -- [~winipanda] the only difference between master

[jira] [Comment Edited] (CALCITE-3998) Bad datatype for sum(n), it should be BIGINT but it is sometimes INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107141#comment-17107141 ] Enrico Olivelli edited comment on CALCITE-3998 at 5/14/20, 9:37 AM:

[jira] [Commented] (CALCITE-3998) Bad datatype for sum(n), it should be BIGINT but it is sometimes INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107141#comment-17107141 ] Enrico Olivelli commented on CALCITE-3998: -- [~winipanda] thank you for debugging. Do you see

[jira] [Commented] (CALCITE-3998) Bad datatype for sum(n), it should be BIGINT but it is sometimes INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107062#comment-17107062 ] Enrico Olivelli commented on CALCITE-3998: -- {quote} I'm curious. why the return type of

[jira] [Commented] (CALCITE-3998) Bad datatype for sum(n), it should be BIGINT but it is sometimes INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107032#comment-17107032 ] Enrico Olivelli commented on CALCITE-3998: -- The test is failing here

[jira] [Commented] (CALCITE-3998) Bad datatype for sum(n), it should be BIGINT but it is sometimes INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107029#comment-17107029 ] Enrico Olivelli commented on CALCITE-3998: -- [~winipanda] thank you so much In the pom.xml we

[jira] [Updated] (CALCITE-3998) Bad datatype for sum(n), it should be BIGINT but it is sometimes INTEGER

[ https://issues.apache.org/jira/browse/CALCITE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli updated CALCITE-3998: - Description: I also noted that sometimes the type of sum(N) where N is an INTEGER

[jira] [Commented] (CALCITE-3997) Problem with MERGE JOIN: java.lang.AssertionError: cannot merge join: left input is not sorted on left keys

[ https://issues.apache.org/jira/browse/CALCITE-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106372#comment-17106372 ] Enrico Olivelli commented on CALCITE-3997: -- can be issue related to CALCITE-3982 ? > Problem

[jira] [Created] (CALCITE-3998) Bad datatype for sum(n), it should be BIGINT but it is sometimes INTEGER

Enrico Olivelli created CALCITE-3998: Summary: Bad datatype for sum(n), it should be BIGINT but it is sometimes INTEGER Key: CALCITE-3998 URL: https://issues.apache.org/jira/browse/CALCITE-3998

[jira] [Created] (CALCITE-3997) Problem with MERGE JOIN: java.lang.AssertionError: cannot merge join: left input is not sorted on left keys

Enrico Olivelli created CALCITE-3997: Summary: Problem with MERGE JOIN: java.lang.AssertionError: cannot merge join: left input is not sorted on left keys Key: CALCITE-3997 URL:

[jira] [Commented] (CALCITE-3826) UPDATE assigns wrong type to bind variables

[ https://issues.apache.org/jira/browse/CALCITE-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17046724#comment-17046724 ] Enrico Olivelli commented on CALCITE-3826: -- Thank you [~zabetak] ! I hope there is any

[jira] [Commented] (CALCITE-3826) UPDATE assigns wrong type to bind variables

[ https://issues.apache.org/jira/browse/CALCITE-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17046647#comment-17046647 ] Enrico Olivelli commented on CALCITE-3826: -- This is the simpler reproducer I have: {code}

[jira] [Comment Edited] (CALCITE-3826) UPDATE assigns wrong type to bind variables

[ https://issues.apache.org/jira/browse/CALCITE-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17046603#comment-17046603 ] Enrico Olivelli edited comment on CALCITE-3826 at 2/27/20 1:10 PM: ---

[jira] [Commented] (CALCITE-3826) UPDATE assigns wrong type to bind variables

[ https://issues.apache.org/jira/browse/CALCITE-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17046603#comment-17046603 ] Enrico Olivelli commented on CALCITE-3826: -- [~zabetak] [~danny0405] the problem is in the

[jira] [Commented] (CALCITE-3826) UPDATE assigns wrong type to bind variables

[ https://issues.apache.org/jira/browse/CALCITE-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17046566#comment-17046566 ] Enrico Olivelli commented on CALCITE-3826: -- In HerdDB we tale the planetario computer with

[jira] [Commented] (CALCITE-3826) UPDATE assigns wrong type to bind variables

[ https://issues.apache.org/jira/browse/CALCITE-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17045396#comment-17045396 ] Enrico Olivelli commented on CALCITE-3826: -- [~danny0405] Thanks for checking is your test

[jira] [Commented] (CALCITE-3769) Deprecate TableScanRule

[ https://issues.apache.org/jira/browse/CALCITE-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17045294#comment-17045294 ] Enrico Olivelli commented on CALCITE-3769: -- In my case the fix was easy, just to return "null"

[jira] [Created] (CALCITE-3826) UPDATE assigns wrong type to bind variables

Enrico Olivelli created CALCITE-3826: Summary: UPDATE assigns wrong type to bind variables Key: CALCITE-3826 URL: https://issues.apache.org/jira/browse/CALCITE-3826 Project: Calcite

[jira] [Commented] (CALCITE-2405) In Babel parser: allow to use some reserved keyword as identifier

[ https://issues.apache.org/jira/browse/CALCITE-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932171#comment-16932171 ] Enrico Olivelli commented on CALCITE-2405: -- [~julianhyde] do you think it is feasible to add

[jira] [Commented] (CALCITE-3347) IndexOutOfBoundsException in FixNullabilityShuttle when using FilterIntoJoinRule

[ https://issues.apache.org/jira/browse/CALCITE-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929995#comment-16929995 ] Enrico Olivelli commented on CALCITE-3347: -- [~julianhyde] In fact the original test case is

[jira] [Commented] (CALCITE-3347) FilterJoinRule throws exception in calcite 1.21. More details in description

[ https://issues.apache.org/jira/browse/CALCITE-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929901#comment-16929901 ] Enrico Olivelli commented on CALCITE-3347: -- The errors happens in the context of unit tests

[jira] [Commented] (CALCITE-2662) Planner: allow parsing directly a stream instead of a java.lang.String

[ https://issues.apache.org/jira/browse/CALCITE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708236#comment-16708236 ] Enrico Olivelli commented on CALCITE-2662: -- Thank you Julian and Vladmin for review   >

[jira] [Commented] (CALCITE-2662) Planner: allow parsing directly a stream instead of a java.lang.String

[ https://issues.apache.org/jira/browse/CALCITE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16705766#comment-16705766 ] Enrico Olivelli commented on CALCITE-2662: -- [~julianhyde] patch is ready from my side. (sorry

[jira] [Commented] (CALCITE-2662) Planner: allow parsing directly a stream instead of a java.lang.String

[ https://issues.apache.org/jira/browse/CALCITE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703710#comment-16703710 ] Enrico Olivelli commented on CALCITE-2662: -- Just because I did not see any test case about the

[jira] [Commented] (CALCITE-2662) Planner: allow parsing directly a stream instead of a java.lang.String

[ https://issues.apache.org/jira/browse/CALCITE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703682#comment-16703682 ] Enrico Olivelli commented on CALCITE-2662: -- I will add tests. As 'originalinput' query seems

[jira] [Commented] (CALCITE-2662) Planner: allow parsing directly a stream instead of a java.lang.String

[ https://issues.apache.org/jira/browse/CALCITE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703362#comment-16703362 ] Enrico Olivelli commented on CALCITE-2662: -- [~julianhyde] I have added a Proof-of-concept

[jira] [Commented] (CALCITE-2662) Planner: allow parsing directly a stream instead of a java.lang.String

[ https://issues.apache.org/jira/browse/CALCITE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16699484#comment-16699484 ] Enrico Olivelli commented on CALCITE-2662: -- Great. I will add the test soon     This is the

[jira] [Commented] (CALCITE-2662) Planner: allow parsing directly a stream instead of a java.lang.String

[ https://issues.apache.org/jira/browse/CALCITE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697810#comment-16697810 ] Enrico Olivelli commented on CALCITE-2662: -- Sorry for late reply. I have updated the patch

[jira] [Created] (CALCITE-2662) Planner: allow parsing directly a stream instead of a java.lang.String

Enrico Olivelli created CALCITE-2662: Summary: Planner: allow parsing directly a stream instead of a java.lang.String Key: CALCITE-2662 URL: https://issues.apache.org/jira/browse/CALCITE-2662

[jira] [Commented] (CALCITE-2405) In Babel parser: allow to use some reserved keyword as identifier

[ https://issues.apache.org/jira/browse/CALCITE-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16672682#comment-16672682 ] Enrico Olivelli commented on CALCITE-2405: -- Great work. I took a look to the patch. I will

[jira] [Commented] (CALCITE-2406) SqlValidator: allow to use raw string literals for timestamps as in MySQL

[ https://issues.apache.org/jira/browse/CALCITE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16672679#comment-16672679 ] Enrico Olivelli commented on CALCITE-2406: -- [~julianhyde] I have updated the title and

[jira] [Updated] (CALCITE-2406) SqlValidator: allow to use raw string literals for timestamps as in MySQL

[ https://issues.apache.org/jira/browse/CALCITE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli updated CALCITE-2406: - Description: I have some case of incompatibility between MySQL (actually on HerdDB

[jira] [Updated] (CALCITE-2406) SqlValidator: allow to use raw string literals for timestamps as in MySQL

[ https://issues.apache.org/jira/browse/CALCITE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli updated CALCITE-2406: - Summary: SqlValidator: allow to use raw string literals for timestamps as in MySQL

[jira] [Commented] (CALCITE-2591) EnumerableDefaults#mergeJoin should throw error and not return incorrect results when inputs are not ordered

[ https://issues.apache.org/jira/browse/CALCITE-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625105#comment-16625105 ] Enrico Olivelli commented on CALCITE-2591: -- this is the patch

[jira] [Created] (CALCITE-2591) EnumerableDefaults#mergeJoin should throw error and not return incorrect results when inputs are not ordered

Enrico Olivelli created CALCITE-2591: Summary: EnumerableDefaults#mergeJoin should throw error and not return incorrect results when inputs are not ordered Key: CALCITE-2591 URL:

[jira] [Commented] (CALCITE-2405) In Babel parser: allow to use some reserved keyword as identifier

[ https://issues.apache.org/jira/browse/CALCITE-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599605#comment-16599605 ] Enrico Olivelli commented on CALCITE-2405: -- One of my customers reported also the will to

[jira] [Commented] (CALCITE-2489) Order of fields in JavaTypeFactoryImpl#createStructType is unstable

[ https://issues.apache.org/jira/browse/CALCITE-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594109#comment-16594109 ] Enrico Olivelli commented on CALCITE-2489: -- Totally agree with Julian > Order of fields in

[jira] [Commented] (CALCITE-2470) RelBuilder.project should combine expressions if underlying node is a Project

[ https://issues.apache.org/jira/browse/CALCITE-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593411#comment-16593411 ] Enrico Olivelli commented on CALCITE-2470: -- The order of the result of

[jira] [Comment Edited] (CALCITE-2457) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CALCITE-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573016#comment-16573016 ] Enrico Olivelli edited comment on CALCITE-2457 at 8/8/18 10:56 AM: ---

[jira] [Commented] (CALCITE-2457) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CALCITE-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573016#comment-16573016 ] Enrico Olivelli commented on CALCITE-2457: -- You will have to upgrade to latest maven surefire

[jira] [Commented] (CALCITE-2395) Support SELECT xxx FROM TABLE FOR UPDATE syntax

[ https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16549816#comment-16549816 ] Enrico Olivelli commented on CALCITE-2395: -- I am worrying about the validator: how can I

[jira] [Commented] (CALCITE-2395) Support SELECT xxx FROM TABLE FOR UPDATE syntax

[ https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16549688#comment-16549688 ] Enrico Olivelli commented on CALCITE-2395: -- Should be consider that the list of identifiers is

[jira] [Commented] (CALCITE-2395) Support SELECT xxx FROM TABLE FOR UPDATE syntax

[ https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16549397#comment-16549397 ] Enrico Olivelli commented on CALCITE-2395: -- Except from SQL92 standard I cannot find any

[jira] [Commented] (CALCITE-2395) Support SELECT xxx FROM TABLE FOR UPDATE syntax

[ https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16547665#comment-16547665 ] Enrico Olivelli commented on CALCITE-2395: -- [~julianhyde] regarding SqlUpdatabilityClause

[jira] [Commented] (CALCITE-2395) Support SELECT xxx FROM TABLE FOR UPDATE syntax

[ https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16547144#comment-16547144 ] Enrico Olivelli commented on CALCITE-2395: -- [~julianhyde] [~michaelmior] I have pushed the

[jira] [Updated] (CALCITE-2406) In Babel parser: allow to use raw string literals for timestamps as in MySQL

[ https://issues.apache.org/jira/browse/CALCITE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli updated CALCITE-2406: - Description: I have some case of incompatibility between MySQL (actually on HerdDB

[jira] [Created] (CALCITE-2406) In Babel parser: allow to use raw string literals for timestamps as in MySQL

Enrico Olivelli created CALCITE-2406: Summary: In Babel parser: allow to use raw string literals for timestamps as in MySQL Key: CALCITE-2406 URL: https://issues.apache.org/jira/browse/CALCITE-2406

[jira] [Created] (CALCITE-2405) In Babel parser: allow to use some reserved keyword as identifier

Enrico Olivelli created CALCITE-2405: Summary: In Babel parser: allow to use some reserved keyword as identifier Key: CALCITE-2405 URL: https://issues.apache.org/jira/browse/CALCITE-2405 Project:

[jira] [Commented] (CALCITE-2304) In Babel parser, allow Hive-style syntax "LEFT SEMI JOIN"

[ https://issues.apache.org/jira/browse/CALCITE-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536708#comment-16536708 ] Enrico Olivelli commented on CALCITE-2304: -- [~julianhyde]   I have tested this change

[jira] [Commented] (CALCITE-2395) Support SELECT xxx FROM TABLE FOR UPDATE syntax

[ https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532993#comment-16532993 ] Enrico Olivelli commented on CALCITE-2395: -- Got it, thanks Julian > Support SELECT xxx FROM

[jira] [Commented] (CALCITE-2395) Support SELECT xxx FROM TABLE FOR UPDATE syntax

[ https://issues.apache.org/jira/browse/CALCITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532444#comment-16532444 ] Enrico Olivelli commented on CALCITE-2395: -- [~julianhyde] [~michaelmior] I am trying to find

[jira] [Created] (CALCITE-2395) Support SELECT xxx FROM TABLE FOR UPDATE syntax

Enrico Olivelli created CALCITE-2395: Summary: Support SELECT xxx FROM TABLE FOR UPDATE syntax Key: CALCITE-2395 URL: https://issues.apache.org/jira/browse/CALCITE-2395 Project: Calcite

[jira] [Commented] (CALCITE-2280) Liberal "babel" parser that accepts all SQL dialects

[ https://issues.apache.org/jira/browse/CALCITE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520767#comment-16520767 ] Enrico Olivelli commented on CALCITE-2280: -- I guess we should wait for Calcite 1.18 for this

[jira] [Commented] (CALCITE-2280) Liberal "babel" parser that accepts all SQL dialects

[ https://issues.apache.org/jira/browse/CALCITE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461549#comment-16461549 ] Enrico Olivelli commented on CALCITE-2280: -- Great work! I have to face several problems due to

[jira] [Commented] (CALCITE-2261) Switch calcite-core to JDK8

[ https://issues.apache.org/jira/browse/CALCITE-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443616#comment-16443616 ] Enrico Olivelli commented on CALCITE-2261: -- [~julianhyde] I have addressed your comments. I

[jira] [Updated] (CALCITE-2261) Switch calcite-core to JDK8

[ https://issues.apache.org/jira/browse/CALCITE-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli updated CALCITE-2261: - Summary: Switch calcite-core to JDK8 (was: Switch calcilte-core to JDK8) > Switch

[jira] [Created] (CALCITE-2261) Switch calcilte-core to JDK8

Enrico Olivelli created CALCITE-2261: Summary: Switch calcilte-core to JDK8 Key: CALCITE-2261 URL: https://issues.apache.org/jira/browse/CALCITE-2261 Project: Calcite Issue Type:

[jira] [Commented] (CALCITE-2172) Document IDE setup for project contribution

[ https://issues.apache.org/jira/browse/CALCITE-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356936#comment-16356936 ] Enrico Olivelli commented on CALCITE-2172: -- My two cents, I am a NetBeans user: 1) clone

[jira] [Commented] (CALCITE-2118) Field names are not preserved by RelToSqlConverter

[ https://issues.apache.org/jira/browse/CALCITE-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311803#comment-16311803 ] Enrico Olivelli commented on CALCITE-2118: -- What is your usecase? Hiw do you get to that plan?

[jira] [Created] (CALCITE-2100) Ability not to use DriverManager to run only the planner

Enrico Olivelli created CALCITE-2100: Summary: Ability not to use DriverManager to run only the planner Key: CALCITE-2100 URL: https://issues.apache.org/jira/browse/CALCITE-2100 Project: Calcite

[jira] [Commented] (CALCITE-2054) Error while validating UPDATE with dynamic parameter in SET clause

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16268176#comment-16268176 ] Enrico Olivelli commented on CALCITE-2054: -- Thank you so much! > Error while validating UPDATE

[jira] [Commented] (CALCITE-2061) Support for dynamic parameters in offset/fetch (limit)

[ https://issues.apache.org/jira/browse/CALCITE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264315#comment-16264315 ] Enrico Olivelli commented on CALCITE-2061: -- Patch updated > Support for dynamic parameters in

[jira] [Commented] (CALCITE-2061) Support for dynamic parameters in offset/fetch (limit)

[ https://issues.apache.org/jira/browse/CALCITE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264200#comment-16264200 ] Enrico Olivelli commented on CALCITE-2061: -- I think I have found the way. Will send updates

[jira] [Commented] (CALCITE-2061) Support for dynamic parameters in offset/fetch (limit)

[ https://issues.apache.org/jira/browse/CALCITE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263920#comment-16263920 ] Enrico Olivelli commented on CALCITE-2061: -- I will fix checkstyle as last task > Support for

[jira] [Commented] (CALCITE-2061) Support for dynamic parameters in offset/fetch (limit)

[ https://issues.apache.org/jira/browse/CALCITE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263919#comment-16263919 ] Enrico Olivelli commented on CALCITE-2061: -- Yep, the error is clear. But I can't find any way

[jira] [Comment Edited] (CALCITE-2061) Support for dynamic parameters in offset/fetch (limit)

[ https://issues.apache.org/jira/browse/CALCITE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262796#comment-16262796 ] Enrico Olivelli edited comment on CALCITE-2061 at 11/22/17 3:31 PM:

[jira] [Commented] (CALCITE-2061) Support for dynamic parameters in offset/fetch (limit)

[ https://issues.apache.org/jira/browse/CALCITE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262796#comment-16262796 ] Enrico Olivelli commented on CALCITE-2061: -- I have integrated your changes [~julianhyde] I

[jira] [Commented] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262762#comment-16262762 ] Enrico Olivelli commented on CALCITE-2054: -- [~julianhyde] I have added the test as requested.

[jira] [Commented] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260745#comment-16260745 ] Enrico Olivelli commented on CALCITE-2054: -- [~julianhyde] I think I have finally found the

[jira] [Commented] (CALCITE-2061) Support for dynamic parameters in offset/fetch (limit)

[ https://issues.apache.org/jira/browse/CALCITE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260401#comment-16260401 ] Enrico Olivelli commented on CALCITE-2061: -- this is the patch

[jira] [Commented] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259783#comment-16259783 ] Enrico Olivelli commented on CALCITE-2054: -- The more I am working on Calcite the more I am

[jira] [Commented] (CALCITE-2061) Support for dynamic parameters in offset/fetch (limit)

[ https://issues.apache.org/jira/browse/CALCITE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258421#comment-16258421 ] Enrico Olivelli commented on CALCITE-2061: -- [~michaelmior] [~julianhyde] I would like to pick

[jira] [Created] (CALCITE-2061) Support for dynamic parameters in offset/fetch (limit)

Enrico Olivelli created CALCITE-2061: Summary: Support for dynamic parameters in offset/fetch (limit) Key: CALCITE-2061 URL: https://issues.apache.org/jira/browse/CALCITE-2061 Project: Calcite

[jira] [Commented] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258410#comment-16258410 ] Enrico Olivelli commented on CALCITE-2054: -- Maybe another alternative option would be to

[jira] [Comment Edited] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257982#comment-16257982 ] Enrico Olivelli edited comment on CALCITE-2054 at 11/18/17 8:27 AM:

[jira] [Comment Edited] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257982#comment-16257982 ] Enrico Olivelli edited comment on CALCITE-2054 at 11/18/17 8:26 AM:

[jira] [Commented] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257982#comment-16257982 ] Enrico Olivelli commented on CALCITE-2054: -- [~julianhyde] I found simpler approach, that is to

[jira] [Commented] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257579#comment-16257579 ] Enrico Olivelli commented on CALCITE-2054: -- Thanks I will debug deeper SqlToRelConverter. I am

[jira] [Commented] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256880#comment-16256880 ] Enrico Olivelli commented on CALCITE-2054: -- I have tried to solve this problem, this is the

[jira] [Updated] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli updated CALCITE-2054: - Description: with a simple UPDATE like: UPDATE mytable set a=? where b=1 I get the

[jira] [Commented] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256604#comment-16256604 ] Enrico Olivelli commented on CALCITE-2054: -- Can you give me some hint? I will be happy to

[jira] [Commented] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254844#comment-16254844 ] Enrico Olivelli commented on CALCITE-2054: -- The error is even with ProjectableFilterableTable

[jira] [Commented] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

[ https://issues.apache.org/jira/browse/CALCITE-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254842#comment-16254842 ] Enrico Olivelli commented on CALCITE-2054: -- [~julianhyde] Do you have time to take at look at

[jira] [Commented] (CALCITE-2039) AssertionError when pushing project to ProjectableFilterableTable

[ https://issues.apache.org/jira/browse/CALCITE-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254841#comment-16254841 ] Enrico Olivelli commented on CALCITE-2039: -- Thank you so much. Will give it a try soon. >

[jira] [Updated] (CALCITE-2039) AssertionError at Mappings.create(Mappings.java:64) with "select 0 as c1,..." and TableProjectableFilterable

[ https://issues.apache.org/jira/browse/CALCITE-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli updated CALCITE-2039: - Attachment: PlannerExampleTest.java attaching very simple reproducer > AssertionError

[jira] [Created] (CALCITE-2054) Parser error on trivial UPDATE with dynamic parameters

Enrico Olivelli created CALCITE-2054: Summary: Parser error on trivial UPDATE with dynamic parameters Key: CALCITE-2054 URL: https://issues.apache.org/jira/browse/CALCITE-2054 Project: Calcite

[jira] [Commented] (CALCITE-2039) AssertionError at Mappings.create(Mappings.java:64) with "select 0 as c1,..." and TableProjectableFilterable

[ https://issues.apache.org/jira/browse/CALCITE-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253405#comment-16253405 ] Enrico Olivelli commented on CALCITE-2039: -- this is the plan Query: UPDATE MYTABLE set id=7

[jira] [Updated] (CALCITE-2039) AssertionError at Mappings.create(Mappings.java:64) with "select 0 as c1,..." and TableProjectableFilterable

[ https://issues.apache.org/jira/browse/CALCITE-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli updated CALCITE-2039: - Attachment: PlannerExampleTest.java run using latest master > AssertionError at

[jira] [Commented] (CALCITE-2039) AssertionError at Mappings.create(Mappings.java:64) with "select 0 as c1,..." and TableProjectableFilterable

[ https://issues.apache.org/jira/browse/CALCITE-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253400#comment-16253400 ] Enrico Olivelli commented on CALCITE-2039: -- I am getting the same error, I have a simpler

[jira] [Commented] (CALCITE-2048) Create a better documentation for the Planner design

[ https://issues.apache.org/jira/browse/CALCITE-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250346#comment-16250346 ] Enrico Olivelli commented on CALCITE-2048: -- Maybe it would be useful a simple guide to plains

  1   2   >