[jira] [Commented] (CALCITE-3395) add BuiltinMethod for Substring(String, int)

[ https://issues.apache.org/jira/browse/CALCITE-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007285#comment-17007285 ] Feng Zhu commented on CALCITE-3395: --- Hi, [~yuanyoujun]. In CALCITE-3563, we have added mechnism in

[jira] [Resolved] (CALCITE-3651) NullPointerException when convert relational algebra that correlates TableFunctionScan

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

[jira] [Updated] (CALCITE-3668) VolcanoPlanner doesn't match all the RelSubSet in matchRecursive

[ https://issues.apache.org/jira/browse/CALCITE-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-3668: Labels: pull-request-available (was: ) > VolcanoPlanner doesn't match all the RelSubSet

[jira] [Commented] (CALCITE-3665) Better estimate join row count when one of the sides is known to be unique

[ https://issues.apache.org/jira/browse/CALCITE-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007152#comment-17007152 ] Rui Wang commented on CALCITE-3665: --- Ah I think I got what you meant: if one side of join is unique,

[jira] [Commented] (CALCITE-3665) Better estimate join row count when one of the sides is known to be unique

[ https://issues.apache.org/jira/browse/CALCITE-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007151#comment-17007151 ] Rui Wang commented on CALCITE-3665: --- Hi [~vladimirsitnikov], could you elaborate a bit on the

[jira] [Comment Edited] (CALCITE-3531) AggregateProjectPullUpConstantsRule should not remove deterministic function group key if the function is dynamic

[ https://issues.apache.org/jira/browse/CALCITE-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007132#comment-17007132 ] Rui Wang edited comment on CALCITE-3531 at 1/2/20 11:48 PM: I found where

[jira] [Commented] (CALCITE-3531) AggregateProjectPullUpConstantsRule should not remove deterministic function group key if the function is dynamic

[ https://issues.apache.org/jira/browse/CALCITE-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007132#comment-17007132 ] Rui Wang commented on CALCITE-3531: --- I found where current_timestamp is defined: SQL standard 2011

[jira] [Created] (CALCITE-3668) VolcanoPlanner doesn't match all the RelSubSet in matchRecursive

Haisheng Yuan created CALCITE-3668: -- Summary: VolcanoPlanner doesn't match all the RelSubSet in matchRecursive Key: CALCITE-3668 URL: https://issues.apache.org/jira/browse/CALCITE-3668 Project:

[jira] [Commented] (CALCITE-3664) Sort in subquery is lost when converting SqlNode to Relnode

[ https://issues.apache.org/jira/browse/CALCITE-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007089#comment-17007089 ] Haisheng Yuan commented on CALCITE-3664: It is expected. See

[jira] [Closed] (CALCITE-500) Ensure EnumerableJoin hashes the smallest input

[ https://issues.apache.org/jira/browse/CALCITE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Sitnikov closed CALCITE-500. - Resolution: Fixed Closing the issue as executor has to be consistent with optimizer.

[jira] [Commented] (CALCITE-3657) EnumerableHashJoin should not use NLogN for costing

[ https://issues.apache.org/jira/browse/CALCITE-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007059#comment-17007059 ] Vladimir Sitnikov commented on CALCITE-3657: I suggest we treat non-equi-join-condition

[jira] [Assigned] (CALCITE-3657) EnumerableHashJoin should not use NLogN for costing

[ https://issues.apache.org/jira/browse/CALCITE-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Sitnikov reassigned CALCITE-3657: -- Assignee: Vladimir Sitnikov > EnumerableHashJoin should not use NLogN for

[jira] [Resolved] (CALCITE-3666) Refine RelMdUniqueKeys and RelMdColumnUniqueness for Calc

[ https://issues.apache.org/jira/browse/CALCITE-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Sitnikov resolved CALCITE-3666. Fix Version/s: 1.22.0 Resolution: Fixed Fixed in

[jira] [Commented] (CALCITE-3663) Support for TRIM function in Bigquery dialect

[ https://issues.apache.org/jira/browse/CALCITE-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17006989#comment-17006989 ] Rui Wang commented on CALCITE-3663: --- Thanks [~dhirenda.gautam] I will help take a look at your PR

[jira] [Updated] (CALCITE-3666) Refine RelMdUniqueKeys and RelMdColumnUniqueness for Calc

[ https://issues.apache.org/jira/browse/CALCITE-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Sitnikov updated CALCITE-3666: --- Summary: Refine RelMdUniqueKeys and RelMdColumnUniqueness for Calc (was: Refine

[jira] [Commented] (CALCITE-3285) EnumerableMergeJoin should support non-equi join conditions

[ https://issues.apache.org/jira/browse/CALCITE-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17006842#comment-17006842 ] Jin Xing commented on CALCITE-3285: --- Hi [~vladimirsitnikov] Yes, you are right, it's a bug. I filed a

[jira] [Updated] (CALCITE-3667) EnumerableMergeJoin should not use take-while enumerator

[ https://issues.apache.org/jira/browse/CALCITE-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-3667: Labels: pull-request-available (was: ) > EnumerableMergeJoin should not use take-while

[jira] [Updated] (CALCITE-3667) EnumerableMergeJoin should not use take-while enumerator

[ https://issues.apache.org/jira/browse/CALCITE-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jin Xing updated CALCITE-3667: -- Description: Currently EnumerableMergeJoin use take-while enumerator [1] to emit values satisfy

[jira] [Created] (CALCITE-3667) EnumerableMergeJoin should not use take-while enumerator

Jin Xing created CALCITE-3667: - Summary: EnumerableMergeJoin should not use take-while enumerator Key: CALCITE-3667 URL: https://issues.apache.org/jira/browse/CALCITE-3667 Project: Calcite

[jira] [Commented] (CALCITE-3285) EnumerableMergeJoin should support non-equi join conditions

[ https://issues.apache.org/jira/browse/CALCITE-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17006820#comment-17006820 ] Jin Xing commented on CALCITE-3285: --- Thanks for ping me [~vladimirsitnikov] I will verify soon ~ >

[jira] [Commented] (CALCITE-3664) Sort in subquery is lost when converting SqlNode to Relnode

[ https://issues.apache.org/jira/browse/CALCITE-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17006813#comment-17006813 ] Jin Xing commented on CALCITE-3664: --- Is it because collation of emp already satisfied the *order by

[jira] [Commented] (CALCITE-3657) EnumerableHashJoin should not use NLogN for costing

[ https://issues.apache.org/jira/browse/CALCITE-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17006806#comment-17006806 ] Ruben Q L commented on CALCITE-3657: Since this ticket is modifying the computeSelfCost of

[jira] [Created] (CALCITE-3666) Refine RelMdColumnUniqueness for Calc

Vladimir Sitnikov created CALCITE-3666: -- Summary: Refine RelMdColumnUniqueness for Calc Key: CALCITE-3666 URL: https://issues.apache.org/jira/browse/CALCITE-3666 Project: Calcite Issue

[jira] [Created] (CALCITE-3665) Better estimate join row count when one of the sides is known to be unique

Vladimir Sitnikov created CALCITE-3665: -- Summary: Better estimate join row count when one of the sides is known to be unique Key: CALCITE-3665 URL: https://issues.apache.org/jira/browse/CALCITE-3665

[jira] [Updated] (CALCITE-3593) RelToSqlConverter changes target of ambiguous HAVING clause with a Project on Filter on Aggregate

[ https://issues.apache.org/jira/browse/CALCITE-3593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-3593: Labels: pull-request-available (was: ) > RelToSqlConverter changes target of ambiguous

[jira] [Updated] (CALCITE-3664) Sort in subquery is lost when converting SqlNode to Relnode

[ https://issues.apache.org/jira/browse/CALCITE-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wang Yanlin updated CALCITE-3664: - Summary: Sort in subquery is lost when converting SqlNode to Relnode (was: Lost sort in

[jira] [Assigned] (CALCITE-3664) Lost sort in subquery when converting SqlNode to Relnode

[ https://issues.apache.org/jira/browse/CALCITE-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wang Yanlin reassigned CALCITE-3664: Assignee: Wang Yanlin > Lost sort in subquery when converting SqlNode to Relnode >

[jira] [Created] (CALCITE-3664) Lost sort in subquery when converting SqlNode to Relnode

Wang Yanlin created CALCITE-3664: Summary: Lost sort in subquery when converting SqlNode to Relnode Key: CALCITE-3664 URL: https://issues.apache.org/jira/browse/CALCITE-3664 Project: Calcite

[jira] [Updated] (CALCITE-3662) Generate wrong SQL when plan contains Project(Sort(Aggregate)) and aggregate field has no alias

[ https://issues.apache.org/jira/browse/CALCITE-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-3662: Labels: pull-request-available (was: ) > Generate wrong SQL when plan contains

[jira] [Updated] (CALCITE-3662) Generate wrong SQL when plan contains Project(Sort(Aggregate)) and aggregate field has no alias

[ https://issues.apache.org/jira/browse/CALCITE-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Jiang updated CALCITE-3662: --- Summary: Generate wrong SQL when plan contains Project(Sort(Aggregate)) and aggregate field has no

[jira] [Commented] (CALCITE-3663) Support for TRIM function in Bigquery dialect

[ https://issues.apache.org/jira/browse/CALCITE-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17006648#comment-17006648 ] Dhirenda Gautam commented on CALCITE-3663: -- Raised the PR