You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/07/29 21:17:04 UTC
[jira] [Created] (PHOENIX-2154) Failure of one mapper should not
affect other mappers in MR index build
James Taylor created PHOENIX-2154:
-------------------------------------
Summary: 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)