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
[
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
[
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:/
[
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
[
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
[
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
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
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
[
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
> --
[
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
> ---
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
[
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
>
[
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
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
[
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
[
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,
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
34 matches
Mail list logo