[
https://issues.apache.org/jira/browse/HIVE-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500994#comment-14500994
]
Sergey Shelukhin commented on HIVE-9824:
----------------------------------------
I'm slowly getting thru the patch. I am skimming lots of the parts of the code
that look like they are almost the same...
3 big questions so far:
1) What is the plan for hybrid join? I see this disables the hybrid join in
code.
2) Someone like [~vikram.dixit] or [~ashutoshc] should probably review (or
skim) the join variations. My brain quickly went out trying to understand code
for all the options.
3) Can you write short description of what code is where and in what order it's
better to read it? Patch is huge...
> LLAP: Native Vectorization of Map Join so previously CPU bound queries shift
> their bottleneck to I/O and make it possible for the rest of LLAP to shine ;)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-9824
> URL: https://issues.apache.org/jira/browse/HIVE-9824
> Project: Hive
> Issue Type: Sub-task
> Reporter: Matt McCline
> Assignee: Matt McCline
> Priority: Critical
> Attachments: HIVE-9824.01.patch, HIVE-9824.02.patch
>
>
> Today's VectorMapJoinOperator is a pass-through that converts each row from a
> vectorized row batch in a Java Object[] row and passes it to the
> MapJoinOperator superclass.
> This enhancement creates specialized vectorized map join operator classes
> that are optimized.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
