[
https://issues.apache.org/jira/browse/CALCITE-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007059#comment-17007059
]
Vladimir Sitnikov commented on CALCITE-3657:
--------------------------------------------
I suggest we treat non-equi-join-condition costing separately. It would touch
all types of joins (e.g. nested loop, hash, merge), and leaving it unaccounted
for a while is ok.
> EnumerableHashJoin should not use NLogN for costing
> ---------------------------------------------------
>
> Key: CALCITE-3657
> URL: https://issues.apache.org/jira/browse/CALCITE-3657
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.21.0
> Reporter: Vladimir Sitnikov
> Assignee: Vladimir Sitnikov
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
