[
https://issues.apache.org/jira/browse/CALCITE-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15714315#comment-15714315
]
Anton Mushin commented on CALCITE-1515:
---
Hi [~julianhyde],
Do you do this issue? C
Julian Hyde created CALCITE-1524:
Summary: Add a project to the planner root so that rules know
which output fields are used
Key: CALCITE-1524
URL: https://issues.apache.org/jira/browse/CALCITE-1524
P
[
https://issues.apache.org/jira/browse/CALCITE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713734#comment-15713734
]
Julian Hyde commented on CALCITE-1523:
--
Yes, I think that would be useful. But if w
[
https://issues.apache.org/jira/browse/CALCITE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713502#comment-15713502
]
Jess Balint commented on CALCITE-1523:
--
I don't see anything preventing conflicting
[
https://issues.apache.org/jira/browse/CALCITE-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-1495:
-
Description:
SemiJoinRule should not apply to RIGHT and FULL JOIN; and it should strip LEFT
JOI
[
https://issues.apache.org/jira/browse/CALCITE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713456#comment-15713456
]
Julian Hyde commented on CALCITE-328:
-
Since we added SemiJoin in CALCITE-368 we will
[
https://issues.apache.org/jira/browse/CALCITE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713452#comment-15713452
]
Julian Hyde commented on CALCITE-330:
-
Since we opted to create {{SemiJoin}} (see CAL
[
https://issues.apache.org/jira/browse/CALCITE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-330:
Description:
Once CALCITE-328 is completed and {{Join}} has a flag
{{eliminateRightDuplicates}}, w
Jess Balint created CALCITE-1523:
Summary: Add RelBuilder field() method to reference aliased
relations not on top of stack
Key: CALCITE-1523
URL: https://issues.apache.org/jira/browse/CALCITE-1523
Pr
[
https://issues.apache.org/jira/browse/CALCITE-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-1495:
-
Summary: SemiJoinRule should not apply to RIGHT and FULL JOIN (was: Add a
rule to convert INNER
[
https://issues.apache.org/jira/browse/CALCITE-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713199#comment-15713199
]
Julian Hyde commented on CALCITE-1495:
--
Changing the subject to refer to the incorr
[
https://issues.apache.org/jira/browse/CALCITE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-375:
Labels: sub-query (was: )
> Support simpler decorrelation transformations for Exists and In
> ---
[
https://issues.apache.org/jira/browse/CALCITE-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-463.
-
Resolution: Not A Problem
I don't believe this is a bug. A table reference (including a table fun
[
https://issues.apache.org/jira/browse/CALCITE-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-863:
Labels: sub-query (was: )
> AssertionError while translating query with UNNEST and having two corr
[
https://issues.apache.org/jira/browse/CALCITE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-709:
Labels: sub-query (was: )
> Errors with LIMIT inside scalar sub-query
> --
[
https://issues.apache.org/jira/browse/CALCITE-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-1045:
-
Labels: sub-query (was: )
> Decorrelate sub-queries in Project and Join
> -
[
https://issues.apache.org/jira/browse/CALCITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-1494:
-
Labels: sub-query (was: )
> Inefficient plan for correlated subqueries
> --
[
https://issues.apache.org/jira/browse/CALCITE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-1511:
-
Labels: sub-query (was: )
> RelDecorrelator's allLessThan failing for NOT EXISTS subquery
> ---
[
https://issues.apache.org/jira/browse/CALCITE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-365:
Labels: sub-query (was: )
> AssertionError while translating query with WITH and correlated sub-qu
[
https://issues.apache.org/jira/browse/CALCITE-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-1513:
-
Labels: sub-query (was: )
> Correlated NOT IN query throws AssertionError
> ---
[
https://issues.apache.org/jira/browse/CALCITE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-1493:
-
Labels: sub-query (was: )
> Wrong plan for NOT IN correlated queries
>
Jess Balint created CALCITE-1522:
Summary: RelBuilder.union() hits assertion when arguments can't
have a common row type
Key: CALCITE-1522
URL: https://issues.apache.org/jira/browse/CALCITE-1522
Proje
[
https://issues.apache.org/jira/browse/CALCITE-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711614#comment-15711614
]
Julian Hyde commented on CALCITE-1519:
--
Can someone please review and +1? I know th
[
https://issues.apache.org/jira/browse/CALCITE-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-1519:
-
Fix Version/s: 1.11.0
> Standardize on "sub-query" rather than "subquery" in class names and com
[
https://issues.apache.org/jira/browse/CALCITE-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maryann Xue resolved CALCITE-1425.
--
Resolution: Fixed
Fixed in
https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commit;h
25 matches
Mail list logo
