[
https://issues.apache.org/jira/browse/PHOENIX-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712655#comment-14712655
]
Ravi Kishore Valeti commented on PHOENIX-2154:
----------------------------------------------
[~chrajeshbab...@gmail.com] [~rajeshbabu]
While working on IndexTool.java for this JIRA, I had a doubt/question on LOCAL
index in the context of IndexTool.java.
In MR Index Build job using IndexTool.java, how are we making sure LOCAL index
builds maintain region co-location with their corresponding Data Table's region?
Code wise, it looks like, we are NOT maintaining this property for LOCAL
indexes which makes both GLOBAL & LOCAL indexes no different from each other
when indexes are created as "Async".
Correct me If my understanding is incorrect.
> Failure of one mapper should not affect other mappers in MR index build
> -----------------------------------------------------------------------
>
> Key: PHOENIX-2154
> URL: https://issues.apache.org/jira/browse/PHOENIX-2154
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: maghamravikiran
> Attachments: IndexTool.java, PHOENIX-2154-WIP.patch,
> PHOENIX-2154-_HBase_Frontdoor_API_WIP.patch
>
>
> Once a mapper in the MR index job succeeds, it should not need to be re-done
> in the event of the failure of one of the other mappers. The initial
> population of an index is based on a snapshot in time, so new rows getting
> *after* the index build has started and/or failed do not impact it.
> Also, there's a 1:1 correspondence between index rows and table rows, so
> there's really no need to dedup. However, the index rows will have a
> different row key than the data table, so I'm not sure how the HFiles are
> split. Will they potentially overlap and is this an issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
