[
https://issues.apache.org/jira/browse/PHOENIX-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371405#comment-15371405
]
ASF GitHub Bot commented on PHOENIX-3061:
-----------------------------------------
GitHub user SsnL opened a pull request:
https://github.com/apache/phoenix/pull/178
[PHOENIX-3061] IndexTool exits 0 even if bulkload failed with error
**What**:
Fix such that when the MapReduce job fails, the job exits with non-zero
code and logs meaningful error message.
**How**:
Modified `IndexTool.configureSubmittableJobUsingDirectApi` and
`IndexTool.configureRunnableJobUsingBulkLoad` so that they don't swallow errors.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SsnL/phoenix PHOENIX_3061
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/phoenix/pull/178.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #178
----
commit 8536ee221d8a706aa5f4ee3628be45b294216d4b
Author: Simon Wang <[email protected]>
Date: 2016-07-11T18:49:24Z
[PHOENIX-3061] IndexTool marks index as ACTIVE and exit 0 even if bulkload
has error
----
> IndexTool marks index as ACTIVE and exit 0 even if bulkload has error
> ---------------------------------------------------------------------
>
> Key: PHOENIX-3061
> URL: https://issues.apache.org/jira/browse/PHOENIX-3061
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.7.0
> Reporter: Tongzhou Wang
> Labels: easyfix
>
> In `IndexTool`, the job exits with code 0 and marks the index table as ACTIVE
> even though MapReduce had error.
> See:
> https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexTool.java#L246-L256
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
