[jira] [Comment Edited] (PHOENIX-2154) Failure of one mapper should not affect other mappers in MR index build

["James Taylor (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679451#comment-14679451 ] 

James Taylor edited comment on PHOENIX-2154 at 8/10/15 1:17 AM:
----------------------------------------------------------------

Would be interested in hearing what you think too, [~jfernando_sfdc], [~elilevine], [~maghamravikiran], [~rvaleti], [~tdsilva].


was (Author: jamestaylor):
Would be interested in hearing what you think too, Jan Fernando, Eli Levine, ravi, Ravi Kishore Valeti, Thomas D'Silva


> 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
>
> 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)