[jira] [Commented] (CALCITE-3144) Add rule, CaseFilteredAggregatorRule, that converts "SUM(CASE WHEN b THEN x END)" to "SUM(x) FILTER (WHERE b)"

[ https://issues.apache.org/jira/browse/CALCITE-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871685#comment-16871685 ] Haisheng Yuan commented on CALCITE-3144: I agree that it might be better to transform it in

[jira] [Updated] (CALCITE-3137) AssertionError when reconstructing STRUCTURED type fields

[ https://issues.apache.org/jira/browse/CALCITE-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3137: --- Description: Add the following test to SqlToRelConverterTest.java. {code:java} @Test

[jira] [Commented] (CALCITE-2624) Add a rule to copy a sort below a join operator

[ https://issues.apache.org/jira/browse/CALCITE-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869083#comment-16869083 ] Haisheng Yuan commented on CALCITE-2624: Nah, physical properties should only be requested by

[jira] [Created] (CALCITE-3138) Restructuring ROW type fields is not supported

Haisheng Yuan created CALCITE-3138: -- Summary: Restructuring ROW type fields is not supported Key: CALCITE-3138 URL: https://issues.apache.org/jira/browse/CALCITE-3138 Project: Calcite Issue

[jira] [Created] (CALCITE-3137) AssertionError when reconstructing STRUCTURED type fields

Haisheng Yuan created CALCITE-3137: -- Summary: AssertionError when reconstructing STRUCTURED type fields Key: CALCITE-3137 URL: https://issues.apache.org/jira/browse/CALCITE-3137 Project: Calcite

[jira] [Commented] (CALCITE-3132) Simply expressions in LogicalFilter generated for subqueries with quantified predicate

[ https://issues.apache.org/jira/browse/CALCITE-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866068#comment-16866068 ] Haisheng Yuan commented on CALCITE-3132: Why need <>($10, 0)? Does $10 represent COUNT()? If it

[jira] [Commented] (CALCITE-3132) Simply expressions in LogicalFilter generated for subqueries with quantified predicate

[ https://issues.apache.org/jira/browse/CALCITE-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866053#comment-16866053 ] Haisheng Yuan commented on CALCITE-3132: Indeed complex. Should {{>($0, $9)}} be enough for

[jira] [Updated] (CALCITE-3132) Simply expressions in LogicalFilter generated for subqueries with quantified predicate

[ https://issues.apache.org/jira/browse/CALCITE-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3132: --- Labels: sub-query (was: ) > Simply expressions in LogicalFilter generated for subqueries

[jira] [Updated] (CALCITE-3124) Infinite rule matching when AggregateRemoveRule is enabled for SUM0

[ https://issues.apache.org/jira/browse/CALCITE-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3124: --- Description: Make the following changes (uncomment return clause) to AggregateRemoveRule,

[jira] [Updated] (CALCITE-3124) Infinite rule matching when AggregateRemoveRule is enabled for SUM0

[ https://issues.apache.org/jira/browse/CALCITE-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3124: --- Description: Make the following changes (uncomment return clause) to /AggregateRemoveRule,

[jira] [Updated] (CALCITE-3124) Infinite rule matching when AggregateRemoveRule is enabled for SUM0

[ https://issues.apache.org/jira/browse/CALCITE-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3124: --- Description: Make the following changes (uncomment return clause) to /AggregateRemoveRule,

[jira] [Updated] (CALCITE-3124) Infinite rule matching when AggregateRemoveRule is enabled for SUM0

[ https://issues.apache.org/jira/browse/CALCITE-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3124: --- Description: Make the following changes (uncomment return clause) to /AggregateRemoveRule,

[jira] [Updated] (CALCITE-3124) Infinite rule matching when AggregateRemoveRule is enabled for SUM0

[ https://issues.apache.org/jira/browse/CALCITE-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3124: --- Description: Make the following changes (uncomment return clause) to /AggregateRemoveRule,

[jira] [Updated] (CALCITE-3124) Infinite rule matching when AggregateRemoveRule is enabled for SUM0

[ https://issues.apache.org/jira/browse/CALCITE-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3124: --- Description: Make the following changes (uncomment return clause) to /AggregateRemoveRule,

[jira] [Created] (CALCITE-3124) Infinite rule matching when AggregateRemoveRule is enabled for SUM0

Haisheng Yuan created CALCITE-3124: -- Summary: Infinite rule matching when AggregateRemoveRule is enabled for SUM0 Key: CALCITE-3124 URL: https://issues.apache.org/jira/browse/CALCITE-3124 Project:

[jira] [Commented] (CALCITE-3087) AggregateOnProjectToAggregateUnifyRule ignores Project incorrectly when its Mapping breaks ordering

[ https://issues.apache.org/jira/browse/CALCITE-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861269#comment-16861269 ] Haisheng Yuan commented on CALCITE-3087: [~donnyzone] Can you log the issue you described and

[jira] [Resolved] (CALCITE-3087) AggregateOnProjectToAggregateUnifyRule ignores Project incorrectly when its Mapping breaks ordering

[ https://issues.apache.org/jira/browse/CALCITE-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved CALCITE-3087. Resolution: Fixed Fix Version/s: 1.20.0 Fixed in

[jira] [Commented] (CALCITE-3121) VolcanoPlanner hangs due to removing ORDER BY from sub-query

[ https://issues.apache.org/jira/browse/CALCITE-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860379#comment-16860379 ] Haisheng Yuan commented on CALCITE-3121: I am neutral on reverting previous changes. The bug

[jira] [Commented] (CALCITE-3122) Convert Pig Latin scripts into Calcite logical plan

[ https://issues.apache.org/jira/browse/CALCITE-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858907#comment-16858907 ] Haisheng Yuan commented on CALCITE-3122: The latest release is

[jira] [Commented] (CALCITE-3122) Convert Pig Latin scripts into Calcite logical plan

[ https://issues.apache.org/jira/browse/CALCITE-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858896#comment-16858896 ] Haisheng Yuan commented on CALCITE-3122: Great. Look forward to your patch. > Convert Pig

[jira] [Updated] (CALCITE-3122) Converte Pig Latin scripts into Calcite logical plan

[ https://issues.apache.org/jira/browse/CALCITE-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3122: --- Summary: Converte Pig Latin scripts into Calcite logical plan (was: Contribution

[jira] [Updated] (CALCITE-3122) Convert Pig Latin scripts into Calcite logical plan

[ https://issues.apache.org/jira/browse/CALCITE-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3122: --- Summary: Convert Pig Latin scripts into Calcite logical plan (was: Converte Pig Latin

[jira] [Commented] (CALCITE-3122) Contribution request: converting Pig Latin scripts into Calcite logical plan

[ https://issues.apache.org/jira/browse/CALCITE-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1685#comment-1685 ] Haisheng Yuan commented on CALCITE-3122: Will the Pig RelBuilder build logical operator instead

[jira] [Commented] (CALCITE-3121) VolcanoPlanner hangs due to removing ORDER BY from sub-query

[ https://issues.apache.org/jira/browse/CALCITE-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858884#comment-16858884 ] Haisheng Yuan commented on CALCITE-3121: This is stack trace: {code:java}

[jira] [Commented] (CALCITE-3121) VolcanoPlanner hangs due to removing ORDER BY from sub-query

[ https://issues.apache.org/jira/browse/CALCITE-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858874#comment-16858874 ] Haisheng Yuan commented on CALCITE-3121: The issue can be reproduced by the following query:

[jira] [Issue Comment Deleted] (CALCITE-3121) VolcanoPlanner hangs due to removing ORDER BY from sub-query

[ https://issues.apache.org/jira/browse/CALCITE-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3121: --- Comment: was deleted (was: The initial planBefore is {code:java}

[jira] [Commented] (CALCITE-3121) VolcanoPlanner hangs due to removing ORDER BY from sub-query

[ https://issues.apache.org/jira/browse/CALCITE-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858870#comment-16858870 ] Haisheng Yuan commented on CALCITE-3121: The initial planBefore is {code:java}

[jira] [Commented] (CALCITE-3087) AggregateOnProjectToAggregateUnifyRule ignores Project incorrectly when its Mapping breaks ordering

[ https://issues.apache.org/jira/browse/CALCITE-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16857048#comment-16857048 ] Haisheng Yuan commented on CALCITE-3087: > RowType and RexNode list are inconsistent. Can you

[jira] [Commented] (CALCITE-3111) Allow custom implementations of Correlate in RelDecorrelator

[ https://issues.apache.org/jira/browse/CALCITE-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856896#comment-16856896 ] Haisheng Yuan commented on CALCITE-3111: It is so sad that Calcite allow optimization directly

[jira] [Commented] (CALCITE-3101) PushDownJoinConditions is not always a valid transformation

[ https://issues.apache.org/jira/browse/CALCITE-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856214#comment-16856214 ] Haisheng Yuan commented on CALCITE-3101: > should the JDBC adapter make the effort to always

[jira] [Commented] (CALCITE-3111) Allow custom implementations of Correlate in RelDecorrelator

[ https://issues.apache.org/jira/browse/CALCITE-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856195#comment-16856195 ] Haisheng Yuan commented on CALCITE-3111: Will your custom Correlate be logical operator or

[jira] [Comment Edited] (CALCITE-3087) AggregateOnProjectToAggregateUnifyRule ignores Project incorrectly when its Mapping breaks ordering

[ https://issues.apache.org/jira/browse/CALCITE-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856178#comment-16856178 ] Haisheng Yuan edited comment on CALCITE-3087 at 6/4/19 10:48 PM: - Can

[jira] [Commented] (CALCITE-3087) AggregateOnProjectToAggregateUnifyRule ignores Project incorrectly when its Mapping breaks ordering

[ https://issues.apache.org/jira/browse/CALCITE-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856178#comment-16856178 ] Haisheng Yuan commented on CALCITE-3087: Can you try this query? It throws type mismatch

[jira] [Commented] (CALCITE-3087) AggregateOnProjectToAggregateUnifyRule ignores Project incorrectly when its Mapping breaks ordering

[ https://issues.apache.org/jira/browse/CALCITE-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856151#comment-16856151 ] Haisheng Yuan commented on CALCITE-3087: I was wrong, the groupSets is adjusted by permute,

[jira] [Created] (CALCITE-3110) Enable parallel execution of parameterized test

Haisheng Yuan created CALCITE-3110: -- Summary: Enable parallel execution of parameterized test Key: CALCITE-3110 URL: https://issues.apache.org/jira/browse/CALCITE-3110 Project: Calcite

[jira] [Updated] (CALCITE-3087) AggregateOnProjectToAggregateUnifyRule ignores Project incorrectly when its Mapping breaks ordering

[ https://issues.apache.org/jira/browse/CALCITE-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3087: --- Summary: AggregateOnProjectToAggregateUnifyRule ignores Project incorrectly when its

[jira] [Commented] (CALCITE-3101) PushDownJoinConditions is not always a valid transformation

[ https://issues.apache.org/jira/browse/CALCITE-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1685#comment-1685 ] Haisheng Yuan commented on CALCITE-3101: What is the point of generating this plan?

[jira] [Updated] (CALCITE-2857) Complicated plan generated for subuqery with both equi and non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-2857: --- Summary: Complicated plan generated for subuqery with both equi and non-equi condition

[jira] [Commented] (CALCITE-2812) Add algebraic operators to allow expressing recursive queries

[ https://issues.apache.org/jira/browse/CALCITE-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855028#comment-16855028 ] Haisheng Yuan commented on CALCITE-2812: SQL Server gives it name MAXRECURSION. The server-wide

[jira] [Commented] (CALCITE-3087) AggregateOnProjectToAggregateUnifyRule cannot ignore Project when its Mapping breaks ordering

[ https://issues.apache.org/jira/browse/CALCITE-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854866#comment-16854866 ] Haisheng Yuan commented on CALCITE-3087: I saw you opened a PR, but I think adding a project

[jira] [Comment Edited] (CALCITE-2812) Add algebraic operators to allow expressing recursive queries

[ https://issues.apache.org/jira/browse/CALCITE-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853769#comment-16853769 ] Haisheng Yuan edited comment on CALCITE-2812 at 6/1/19 5:32 PM: Looks

[jira] [Commented] (CALCITE-2812) Add algebraic operators to allow expressing recursive queries

[ https://issues.apache.org/jira/browse/CALCITE-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853769#comment-16853769 ] Haisheng Yuan commented on CALCITE-2812: Looks like it is maven-surefire-plugin's issue. I

[jira] [Commented] (CALCITE-2812) Add algebraic operators to allow expressing recursive queries

[ https://issues.apache.org/jira/browse/CALCITE-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853751#comment-16853751 ] Haisheng Yuan commented on CALCITE-2812: I have the same finding. It has nothing to do with

[jira] [Commented] (CALCITE-2944) Deprecate Aggregate indicators and remove fields where possible

[ https://issues.apache.org/jira/browse/CALCITE-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853516#comment-16853516 ] Haisheng Yuan commented on CALCITE-2944: Sure, I will leave it to you. Thanks! > Deprecate

[jira] [Commented] (CALCITE-2944) Deprecate Aggregate indicators and remove fields where possible

[ https://issues.apache.org/jira/browse/CALCITE-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853501#comment-16853501 ] Haisheng Yuan commented on CALCITE-2944: My mistake. I will update it to stop using the API

[jira] [Resolved] (CALCITE-2944) Deprecate Aggregate indicators and remove fields where possible

[ https://issues.apache.org/jira/browse/CALCITE-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved CALCITE-2944. Resolution: Fixed Fix Version/s: 1.20.0 Fixed in

[jira] [Commented] (CALCITE-3089) Deprecate EquiJoin

[ https://issues.apache.org/jira/browse/CALCITE-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852685#comment-16852685 ] Haisheng Yuan commented on CALCITE-3089: Working on this. > Deprecate EquiJoin >

[jira] [Commented] (CALCITE-2973) Allow theta joins that have equi conditions to be executed using a hash join algorithm

[ https://issues.apache.org/jira/browse/CALCITE-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852684#comment-16852684 ] Haisheng Yuan commented on CALCITE-2973: Agree, I think this patch can be done after 3089 is

[jira] [Commented] (CALCITE-2812) Add algebraic operators to allow expressing recursive queries

[ https://issues.apache.org/jira/browse/CALCITE-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852445#comment-16852445 ] Haisheng Yuan commented on CALCITE-2812: With this patch, the test suite in master branch can't

[jira] [Updated] (CALCITE-2857) SemiJoin extends Join directly instead of EquiJoin to support non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-2857: --- Labels: sub-query (was: ) > SemiJoin extends Join directly instead of EquiJoin to support

[jira] [Commented] (CALCITE-2969) Improve design of join-like relational expressions

[ https://issues.apache.org/jira/browse/CALCITE-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851365#comment-16851365 ] Haisheng Yuan commented on CALCITE-2969: Regarding

[jira] [Commented] (CALCITE-2969) Improve design of join-like relational expressions

[ https://issues.apache.org/jira/browse/CALCITE-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851339#comment-16851339 ] Haisheng Yuan commented on CALCITE-2969: +1, I think it is good to go, except for small comment

[jira] [Commented] (CALCITE-3086) MULTI_FUNCTION mapping is not implemented

[ https://issues.apache.org/jira/browse/CALCITE-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851246#comment-16851246 ] Haisheng Yuan commented on CALCITE-3086: Yes, I agree with your observations. Since my

[jira] [Commented] (CALCITE-3086) MULTI_FUNCTION mapping is not implemented

[ https://issues.apache.org/jira/browse/CALCITE-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850043#comment-16850043 ] Haisheng Yuan commented on CALCITE-3086: [~donnyzone] Sure, thanks! > MULTI_FUNCTION mapping

[jira] [Assigned] (CALCITE-3086) MULTI_FUNCTION mapping is not implemented

[ https://issues.apache.org/jira/browse/CALCITE-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan reassigned CALCITE-3086: -- Assignee: Feng Zhu > MULTI_FUNCTION mapping is not implemented >

[jira] [Resolved] (CALCITE-3077) Rewrite CUBE queries in SparkSqlDialect

[ https://issues.apache.org/jira/browse/CALCITE-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved CALCITE-3077. Resolution: Fixed Fix Version/s: 1.20.0 Fixed in

[jira] [Commented] (CALCITE-3087) Mappings.apply2 doesn't keep order

[ https://issues.apache.org/jira/browse/CALCITE-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847919#comment-16847919 ] Haisheng Yuan commented on CALCITE-3087: What is worse,

[jira] [Commented] (CALCITE-3077) Rewrite CUBE queries in SparkSqlDialect

[ https://issues.apache.org/jira/browse/CALCITE-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847203#comment-16847203 ] Haisheng Yuan commented on CALCITE-3077: Yes, SQL language is more stable and standard. Thanks

[jira] [Updated] (CALCITE-3089) Deprecate EquiJoin

[ https://issues.apache.org/jira/browse/CALCITE-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3089: --- Description: EquiJoin should be replaced by Join with equiConds and nonEquiConds (empty if

[jira] [Assigned] (CALCITE-3089) Deprecate EquiJoin

[ https://issues.apache.org/jira/browse/CALCITE-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan reassigned CALCITE-3089: -- Assignee: Haisheng Yuan > Deprecate EquiJoin > -- > >

[jira] [Created] (CALCITE-3089) Deprecate EquiJoin

Haisheng Yuan created CALCITE-3089: -- Summary: Deprecate EquiJoin Key: CALCITE-3089 URL: https://issues.apache.org/jira/browse/CALCITE-3089 Project: Calcite Issue Type: Improvement

[jira] [Commented] (CALCITE-3077) Rewrite CUBE queries in SparkSqlDialect

[ https://issues.apache.org/jira/browse/CALCITE-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847030#comment-16847030 ] Haisheng Yuan commented on CALCITE-3077: [~donnyzone] Just out of curious, are you migrating

[jira] [Commented] (CALCITE-3085) Unused stack field in RelShuttleImpl

[ https://issues.apache.org/jira/browse/CALCITE-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847011#comment-16847011 ] Haisheng Yuan commented on CALCITE-3085: I can't find any usage of the stack either. So I agree

[jira] [Commented] (CALCITE-3079) Successive dependent windows cannot be implemented in same expression level

[ https://issues.apache.org/jira/browse/CALCITE-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846988#comment-16846988 ] Haisheng Yuan commented on CALCITE-3079: [~donnyzone] Thanks for trying. We should fix

[jira] [Created] (CALCITE-3087) Mappings.apply2 doesn't keep order

Haisheng Yuan created CALCITE-3087: -- Summary: Mappings.apply2 doesn't keep order Key: CALCITE-3087 URL: https://issues.apache.org/jira/browse/CALCITE-3087 Project: Calcite Issue Type: Bug

[jira] [Created] (CALCITE-3086) MULTI_FUNCTION mapping is not implemented

Haisheng Yuan created CALCITE-3086: -- Summary: MULTI_FUNCTION mapping is not implemented Key: CALCITE-3086 URL: https://issues.apache.org/jira/browse/CALCITE-3086 Project: Calcite Issue

[jira] [Commented] (CALCITE-3079) Successive dependent windows cannot be implemented in same expression level

[ https://issues.apache.org/jira/browse/CALCITE-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846210#comment-16846210 ] Haisheng Yuan commented on CALCITE-3079: Instead of splitting wrongly nested window in Project,

[jira] [Commented] (CALCITE-2648) Output collation of EnumerableWindow is not consistent with its implementation

[ https://issues.apache.org/jira/browse/CALCITE-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846193#comment-16846193 ] Haisheng Yuan commented on CALCITE-2648: Whether EnumerableWindow should preserve the order is

[jira] [Issue Comment Deleted] (CALCITE-2648) Output collation of EnumerableWindow is not consistent with its implementation

[ https://issues.apache.org/jira/browse/CALCITE-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-2648: --- Comment: was deleted (was: Agree with Julian. Window is not required to preserve order on

[jira] [Commented] (CALCITE-3079) Successive dependent windows cannot be implemented in same expression level

[ https://issues.apache.org/jira/browse/CALCITE-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846117#comment-16846117 ] Haisheng Yuan commented on CALCITE-3079: I never see nested window in query plan, why do you

[jira] [Assigned] (CALCITE-1794) Simplify AND numeric comparisons when overlapping

[ https://issues.apache.org/jira/browse/CALCITE-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan reassigned CALCITE-1794: -- Assignee: Haisheng Yuan > Simplify AND numeric comparisons when overlapping >

[jira] [Resolved] (CALCITE-2371) how to perform joins in mongodb using model json in calcite

[ https://issues.apache.org/jira/browse/CALCITE-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved CALCITE-2371. Resolution: Invalid > how to perform joins in mongodb using model json in calcite >

[jira] [Comment Edited] (CALCITE-2624) Add a rule to copy a sort below a join operator

[ https://issues.apache.org/jira/browse/CALCITE-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840696#comment-16840696 ] Haisheng Yuan edited comment on CALCITE-2624 at 5/15/19 7:39 PM: -

[jira] [Commented] (CALCITE-2624) Add a rule to copy a sort below a join operator

[ https://issues.apache.org/jira/browse/CALCITE-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840696#comment-16840696 ] Haisheng Yuan commented on CALCITE-2624: Thanks for the explanation, [~rubenql]. I see you

[jira] [Resolved] (CALCITE-3028) Support FULL OUTER JOIN with AggregateJoinTransposeRule

[ https://issues.apache.org/jira/browse/CALCITE-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved CALCITE-3028. Resolution: Fixed Fix Version/s: 1.20.0 Fixed in

[jira] [Resolved] (CALCITE-2936) Simplify EXISTS or NOT EXISTS sub-query that has "GROUP BY ()"

[ https://issues.apache.org/jira/browse/CALCITE-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved CALCITE-2936. Resolution: Fixed Fix Version/s: 1.20.0 Fixed in

[jira] [Commented] (CALCITE-2624) Add a rule to copy a sort below a join operator

[ https://issues.apache.org/jira/browse/CALCITE-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839978#comment-16839978 ] Haisheng Yuan commented on CALCITE-2624: The PR is mixing physical property enforcement with

[jira] [Commented] (CALCITE-3041) Query runs endless when setImportance to 0

[ https://issues.apache.org/jira/browse/CALCITE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830844#comment-16830844 ] Haisheng Yuan commented on CALCITE-3041: [~danny0405] Go ahead, thanks! > Query runs endless

[jira] [Updated] (CALCITE-3041) Query runs endless when setImportance to 0

[ https://issues.apache.org/jira/browse/CALCITE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3041: --- Description: Make the following changes: {code:diff} ---

[jira] [Updated] (CALCITE-3041) Query runs endless when setImportance to 0

[ https://issues.apache.org/jira/browse/CALCITE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-3041: --- Description: Make the following changes: {code:java} ---

[jira] [Created] (CALCITE-3041) Query runs endless when setImportance to 0

Haisheng Yuan created CALCITE-3041: -- Summary: Query runs endless when setImportance to 0 Key: CALCITE-3041 URL: https://issues.apache.org/jira/browse/CALCITE-3041 Project: Calcite Issue

[jira] [Commented] (CALCITE-3031) AssertionError: correlation id $cor0 not found in correlation list []

[ https://issues.apache.org/jira/browse/CALCITE-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829824#comment-16829824 ] Haisheng Yuan commented on CALCITE-3031: I have a similar patch with yours. But since it is

[jira] [Assigned] (CALCITE-3031) AssertionError: correlation id $cor0 not found in correlation list []

[ https://issues.apache.org/jira/browse/CALCITE-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan reassigned CALCITE-3031: -- Assignee: Vineet Garg (was: Haisheng Yuan) > AssertionError: correlation id $cor0

[jira] [Commented] (CALCITE-2969) Improve design of join-like relational expressions

[ https://issues.apache.org/jira/browse/CALCITE-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829782#comment-16829782 ] Haisheng Yuan commented on CALCITE-2969: The PR in Github is stuffed with our comments, I will

[jira] [Resolved] (CALCITE-2292) Query result is wrong when table is implemented with FilterableTable and the sql has multiple where conditions

[ https://issues.apache.org/jira/browse/CALCITE-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan resolved CALCITE-2292. Resolution: Fixed Fix Version/s: 1.20.0 Fixed in

[jira] [Commented] (CALCITE-2948) Complicated logical plan generated for in subquery with non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1682#comment-1682 ] Haisheng Yuan commented on CALCITE-2948: My mistake, the plan is not incorrect. We are not

[jira] [Comment Edited] (CALCITE-2948) Complicated logical plan generated for in subquery with non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1682#comment-1682 ] Haisheng Yuan edited comment on CALCITE-2948 at 4/29/19 4:07 AM: - My

[jira] [Commented] (CALCITE-2948) Complicated logical plan generated for in subquery with non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16828874#comment-16828874 ] Haisheng Yuan commented on CALCITE-2948: SubqueryRemoveRule transform correlated subquery to

[jira] [Assigned] (CALCITE-3031) AssertionError: correlation id $cor0 not found in correlation list []

[ https://issues.apache.org/jira/browse/CALCITE-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan reassigned CALCITE-3031: -- Assignee: Haisheng Yuan > AssertionError: correlation id $cor0 not found in

[jira] [Created] (CALCITE-3031) AssertionError: correlation id $cor0 not found in correlation list []

Haisheng Yuan created CALCITE-3031: -- Summary: AssertionError: correlation id $cor0 not found in correlation list [] Key: CALCITE-3031 URL: https://issues.apache.org/jira/browse/CALCITE-3031 Project:

[jira] [Commented] (CALCITE-2948) Complicated logical plan generated for in subquery with non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16828858#comment-16828858 ] Haisheng Yuan commented on CALCITE-2948: The problem is that we always generate inner

[jira] [Commented] (CALCITE-2948) Complicated logical plan generated for in subquery with non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16828857#comment-16828857 ] Haisheng Yuan commented on CALCITE-2948: Well, I found that the plan described in issue can

[jira] [Commented] (CALCITE-2948) Complicated logical plan generated for in subquery with non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16828850#comment-16828850 ] Haisheng Yuan commented on CALCITE-2948: I think you have missed our last conversation that

[jira] [Commented] (CALCITE-3014) SqlConformanceEnum is hard coded in a few places

[ https://issues.apache.org/jira/browse/CALCITE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827846#comment-16827846 ] Haisheng Yuan commented on CALCITE-3014: For federated system, someone may want to join tables

[jira] [Commented] (CALCITE-2948) Complicated logical plan generated for in subquery with non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827429#comment-16827429 ] Haisheng Yuan commented on CALCITE-2948: I see your points. But I think we should not aim at

[jira] [Commented] (CALCITE-2948) Complicated logical plan generated for in subquery with non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827376#comment-16827376 ] Haisheng Yuan commented on CALCITE-2948: {quote} what kinds of 2 RelNodes are equavelent

[jira] [Commented] (CALCITE-2948) Complicated logical plan generated for in subquery with non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827084#comment-16827084 ] Haisheng Yuan commented on CALCITE-2948: [~danny0405] Let's first just focus on

[jira] [Updated] (CALCITE-2948) Complicated logical plan generated for in subquery with non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haisheng Yuan updated CALCITE-2948: --- Summary: Complicated logical plan generated for in subquery with non-equi condition (was:

[jira] [Commented] (CALCITE-2948) SqlToRelConverter generates complicated logical plan for in subquery with non-equi condition

[ https://issues.apache.org/jira/browse/CALCITE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827073#comment-16827073 ] Haisheng Yuan commented on CALCITE-2948: What about $b % 2, CASE WHEN...? Changing pattern will

[jira] [Commented] (CALCITE-3021) ArrayEqualityComparer should use Arrays#deepEquals/deepHashCode instead of Arrays#equals/hashCode

[ https://issues.apache.org/jira/browse/CALCITE-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827060#comment-16827060 ] Haisheng Yuan commented on CALCITE-3021: [~rubenql] Yes. Sorry for my mistake. >

<    4   5   6   7   8   9   10   11   >