phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-1556) Base hash versus sort merge join decision on how much data will be scanned
Date Fri, 20 Oct 2017 21:13:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Taylor updated PHOENIX-1556:
----------------------------------
    Summary: Base hash versus sort merge join decision on how much data will be scanned  (was:
Base hash join versus many-to-many decision on how many guideposts will be traversed for RHS
table(s))

> Base hash versus sort merge join decision on how much data will be scanned
> --------------------------------------------------------------------------
>
>                 Key: PHOENIX-1556
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1556
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: Maryann Xue
>              Labels: calcite
>
> At compile time, we know how many guideposts (i.e. how many bytes) will be scanned for
the RHS table. We should, by default, base the decision of using the hash-join verus many-to-many
join on this information.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message