[
https://issues.apache.org/jira/browse/PHOENIX-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720910#comment-14720910
]
Hudson commented on PHOENIX-2154:
---------------------------------
SUCCESS: Integrated in Phoenix-master #883 (See
[https://builds.apache.org/job/Phoenix-master/883/])
PHOENIX-2154 Failure of one mapper should not affect other mappers in MR index
build (Ravi Kishore Valeti) (tdsilva: rev
16fcdf9e1c116758027b79a24f9ec701cb63496f)
*
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexToolUtil.java
*
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/PhoenixIndexImportDirectMapper.java
* phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexTool.java
*
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/DirectHTableWriter.java
* phoenix-core/src/it/java/org/apache/phoenix/mapreduce/IndexToolIT.java
*
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/PhoenixIndexToolReducer.java
> 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: Ravi Kishore Valeti
> Attachments: IndexTool.java, PHOENIX-2154-WIP.patch,
> PHOENIX-2154-_HBase_Frontdoor_API_WIP.patch,
> PHOENIX-2154-_HBase_Frontdoor_API_v1.patch,
> PHOENIX-2154-_HBase_Frontdoor_API_v2.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)
