[jira] [Created] (CALCITE-4682) Cost of Operator limit may break cumulative cost calculation assumption

ZiLin Chen created CALCITE-4682: --- Summary: Cost of Operator limit may break cumulative cost calculation assumption Key: CALCITE-4682 URL: https://issues.apache.org/jira/browse/CALCITE-4682 Project: Calc

[jira] [Commented] (CALCITE-4681) Rule operand match specific shape with or without RelSubset.class/RelNode.class

[ https://issues.apache.org/jira/browse/CALCITE-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376381#comment-17376381 ] Roman Kondakov commented on CALCITE-4681: - I think this problem may be related

[jira] [Resolved] (CALCITE-4668) RelBuilder.join should convert Correlate to Join if correlation variable is unused

[ https://issues.apache.org/jira/browse/CALCITE-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stamatis Zampetakis resolved CALCITE-4668. -- Resolution: Fixed Fixed in [a59693e0342f52fd9eeb48bf55e7f4d02913fa79|https:/

[jira] [Commented] (CALCITE-3524) Add methods to RelBuilder to create RexSubQuery

[ https://issues.apache.org/jira/browse/CALCITE-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376404#comment-17376404 ] Amir Gajst commented on CALCITE-3524: - [~julianhyde] I like that solution. I'll pro

[jira] [Commented] (CALCITE-4681) Rule operand match specific shape with or without RelSubset.class/RelNode.class

[ https://issues.apache.org/jira/browse/CALCITE-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376406#comment-17376406 ] ZiLin Chen commented on CALCITE-4681: - No, with LogicalJoin we can only pass by tho

[jira] [Assigned] (CALCITE-4668) RelBuilder.join should convert Correlate to Join if correlation variable is unused

[ https://issues.apache.org/jira/browse/CALCITE-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stamatis Zampetakis reassigned CALCITE-4668: Assignee: James Starr > RelBuilder.join should convert Correlate to Join

[jira] [Created] (CALCITE-4683) In-list to join with new project generated cause replaced root leaves property to be missing

yanjing.wang created CALCITE-4683: - Summary: In-list to join with new project generated cause replaced root leaves property to be missing Key: CALCITE-4683 URL: https://issues.apache.org/jira/browse/CALCITE-4683

[jira] [Commented] (CALCITE-4681) Rule operand match specific shape with or without RelSubset.class/RelNode.class

[ https://issues.apache.org/jira/browse/CALCITE-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376422#comment-17376422 ] Roman Kondakov commented on CALCITE-4681: - You can add a predicate to the XXX o

[jira] [Updated] (CALCITE-4683) In-list to join with new project generated cause replaced root leaves property to be missing

[ https://issues.apache.org/jira/browse/CALCITE-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yanjing.wang updated CALCITE-4683: -- Description: When Calcite converts a in list to a join, the original relational algebra root

[jira] [Commented] (CALCITE-4681) Rule operand match specific shape with or without RelSubset.class/RelNode.class

[ https://issues.apache.org/jira/browse/CALCITE-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376451#comment-17376451 ] ZiLin Chen commented on CALCITE-4681: - I had tried the way using predicate restrict

[jira] [Updated] (CALCITE-4683) In-list to join with new project generated cause replaced root leaves property to be missing

[ https://issues.apache.org/jira/browse/CALCITE-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-4683: Labels: pull-request-available (was: ) > In-list to join with new project generated caus

[jira] [Resolved] (CALCITE-4640) Propagate table scan hints to JDBC

[ https://issues.apache.org/jira/browse/CALCITE-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danny Chen resolved CALCITE-4640. - Fix Version/s: 1.28.0 Resolution: Fixed Fixed in [44dfb70|https://github.com/apache/cal

[jira] [Updated] (CALCITE-4680) AssertionError: contains $cor1, while converting SQL query containing UNNEST to logical plan using subquery expansion

[ https://issues.apache.org/jira/browse/CALCITE-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Rebele updated CALCITE-4680: --- Summary: AssertionError: contains $cor1, while converting SQL query containing UNNEST to lo

[jira] [Commented] (CALCITE-4680) AssertionError: contains $cor1, while converting SQL query containing UNNEST to logical plan using subquery expansion

[ https://issues.apache.org/jira/browse/CALCITE-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376573#comment-17376573 ] Thomas Rebele commented on CALCITE-4680: Thank you, the problem goes away after

[jira] [Created] (CALCITE-4684) PlannerImpl forced restructure after converting to RelNode

Sicheng Pan created CALCITE-4684: Summary: PlannerImpl forced restructure after converting to RelNode Key: CALCITE-4684 URL: https://issues.apache.org/jira/browse/CALCITE-4684 Project: Calcite

[jira] [Updated] (CALCITE-4684) PlannerImpl forced restructure after converting to RelNode

[ https://issues.apache.org/jira/browse/CALCITE-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sicheng Pan updated CALCITE-4684: - Component/s: core > PlannerImpl forced restructure after converting to RelNode > --

[jira] [Updated] (CALCITE-4684) PlannerImpl forced restructure after converting to RelNode

[ https://issues.apache.org/jira/browse/CALCITE-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sicheng Pan updated CALCITE-4684: - Labels: easyfix (was: ) > PlannerImpl forced restructure after converting to RelNode > ---

[jira] [Created] (CALCITE-4685) Server implementation (executor) do not support DDL statements with constraints

Sicheng Pan created CALCITE-4685: Summary: Server implementation (executor) do not support DDL statements with constraints Key: CALCITE-4685 URL: https://issues.apache.org/jira/browse/CALCITE-4685 Pro

[jira] [Updated] (CALCITE-4684) PlannerImpl forced restructure after converting to RelNode

[ https://issues.apache.org/jira/browse/CALCITE-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sicheng Pan updated CALCITE-4684: - Fix Version/s: (was: 1.28.0) > PlannerImpl forced restructure after converting to RelNode >

[jira] [Updated] (CALCITE-4685) Server implementation (executor) do not support DDL statements with constraints

[ https://issues.apache.org/jira/browse/CALCITE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sicheng Pan updated CALCITE-4685: - Fix Version/s: (was: 1.28.0) > Server implementation (executor) do not support DDL statemen

[jira] [Created] (CALCITE-4686) SubQueryRemoveRule.matchJoin should correctly rewrite all sub-queries

James Starr created CALCITE-4686: Summary: SubQueryRemoveRule.matchJoin should correctly rewrite all sub-queries Key: CALCITE-4686 URL: https://issues.apache.org/jira/browse/CALCITE-4686 Project: Calc

[jira] [Assigned] (CALCITE-4686) SubQueryRemoveRule.matchJoin should correctly rewrite all sub-queries

[ https://issues.apache.org/jira/browse/CALCITE-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Starr reassigned CALCITE-4686: Assignee: James Starr > SubQueryRemoveRule.matchJoin should correctly rewrite all sub-qu

[jira] [Commented] (CALCITE-4686) SubQueryRemoveRule.matchJoin should correctly rewrite all sub-queries

[ https://issues.apache.org/jira/browse/CALCITE-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376906#comment-17376906 ] James Starr commented on CALCITE-4686: -- Sub queries in ON conditions do not work,

[jira] [Updated] (CALCITE-4686) SubQueryRemoveRule.matchJoin should correctly rewrite all sub-queries

[ https://issues.apache.org/jira/browse/CALCITE-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-4686: Labels: pull-request-available (was: ) > SubQueryRemoveRule.matchJoin should correctly r

[jira] [Commented] (CALCITE-4683) In-list to join with new project generated cause replaced root leaves property to be missing

[ https://issues.apache.org/jira/browse/CALCITE-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376913#comment-17376913 ] Julian Hyde commented on CALCITE-4683: -- Can you change the subject to describe the

[jira] [Commented] (CALCITE-4682) Cost of Operator limit may break cumulative cost calculation assumption

[ https://issues.apache.org/jira/browse/CALCITE-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376915#comment-17376915 ] Julian Hyde commented on CALCITE-4682: -- Can you please describe the "problem about

[jira] [Commented] (CALCITE-4681) Rule operand match specific shape with or without RelSubset.class/RelNode.class

[ https://issues.apache.org/jira/browse/CALCITE-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376919#comment-17376919 ] Julian Hyde commented on CALCITE-4681: -- What's wrong with the 'normal' way of writ

[jira] [Updated] (CALCITE-4683) Conversion to relational algebra failed to preserve datatypes when converting In-list to join with new project generated

[ https://issues.apache.org/jira/browse/CALCITE-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yanjing.wang updated CALCITE-4683: -- Summary: Conversion to relational algebra failed to preserve datatypes when converting In-lis

[jira] [Commented] (CALCITE-4683) Conversion to relational algebra failed to preserve datatypes when converting In-list to join with new project generated

[ https://issues.apache.org/jira/browse/CALCITE-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376957#comment-17376957 ] yanjing.wang commented on CALCITE-4683: --- Thanks [~julianhyde], I think I need som

[jira] [Commented] (CALCITE-3775) Implicit lookup methods in SimpleCalciteSchema ignore case sensitivity parameter

[ https://issues.apache.org/jira/browse/CALCITE-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376977#comment-17376977 ] Feng Zhu commented on CALCITE-3775: --- Fixed in [https://github.com/apache/calcite/com

[jira] [Closed] (CALCITE-3775) Implicit lookup methods in SimpleCalciteSchema ignore case sensitivity parameter

[ https://issues.apache.org/jira/browse/CALCITE-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Zhu closed CALCITE-3775. - Resolution: Fixed > Implicit lookup methods in SimpleCalciteSchema ignore case sensitivity > parameter

[jira] [Commented] (CALCITE-3329) Implement osquery for OS adapter

[ https://issues.apache.org/jira/browse/CALCITE-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376983#comment-17376983 ] Forward Xu commented on CALCITE-3329: - hi [~julianhyde]  Sorry, it took so long to

[jira] [Commented] (CALCITE-4681) Rule operand match specific shape with or without RelSubset.class/RelNode.class

[ https://issues.apache.org/jira/browse/CALCITE-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17377089#comment-17377089 ] ZiLin Chen commented on CALCITE-4681: - JoinReorder rules like JoinAssociateRule or

[jira] [Updated] (CALCITE-4682) Cost of Operator limit may break cumulative cost calculation assumption

[ https://issues.apache.org/jira/browse/CALCITE-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZiLin Chen updated CALCITE-4682: Description: Any way calcite can provide to solve the problem about cost of limit operator? Limi