[
https://issues.apache.org/jira/browse/PHOENIX-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257816#comment-14257816
]
James Taylor commented on PHOENIX-1179:
---------------------------------------
You likely already saw this comment:
https://issues.apache.org/jira/browse/PHOENIX-1179?focusedCommentId=14211790&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14211790
I think you probably need either Phoenix to "know" when to use many-to-many
join strategy (PHOENIX-1556), or a fallback mechanism when you encounter the
InsufficientMemoryException (PHOENIX-1555), or a means of "telling" Phoenix to
use many-to-many join strategy (PHOENIX-1557). I think currently, it'll use the
hash join strategy if the compiler says it's able to (even if at runtime it
will fail), so this isn't helping you much.
The last one (PHOENIX-1557) may be doable as a small patch if you're up for it,
[~alexdl].
> Support many-to-many joins
> --------------------------
>
> Key: PHOENIX-1179
> URL: https://issues.apache.org/jira/browse/PHOENIX-1179
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Maryann Xue
> Fix For: 4.3, 3.3
>
> Attachments: 1179.patch
>
>
> Enhance our join capabilities to support many-to-many joins where the size of
> both sides of the join are too big to fit into memory (and thus cannot use
> our hash join mechanism). One technique would be to order both sides of the
> join by their join key and merge sort the results on the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
