crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Wills (JIRA)" <>
Subject [jira] [Commented] (CRUNCH-216) Transpose arguments in MapsideJoinStrategy.join
Date Mon, 19 Aug 2013 15:50:48 GMT


Josh Wills commented on CRUNCH-216:

I don't know that I have a great way of handling it. Just spitballing this: join() could,
by default, use the getSize() methods on the left and right table to decide which of the two
was smaller, and we could add an argument or have another method that would allow the developer
to explicitly specify the ordering, something like joinSmallerToLarger(). It's the least bad
way I see to make all of the different join() methods consistent with each other, but it involves
making the Crunch libs more clever than I generally like them to be.
> Transpose arguments in MapsideJoinStrategy.join
> -----------------------------------------------
>                 Key: CRUNCH-216
>                 URL:
>             Project: Crunch
>          Issue Type: Improvement
>            Reporter: Gabriel Reid
> The MapsideJoinStrategy currently specifies that the smaller table in the join (i.e.
the table to be replicated and loaded in memory) should be on the right-hand side of the join.
> This is the opposite of what is done in all other join strategies, making it impossible
to just switch out another join strategy for a MapsideJoinStrategy. The MapsideJoinStrategy
could be brought in line with the other JoinStrategies to expect the smaller of two tables
to be provided as the left-side table.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message