[
https://issues.apache.org/jira/browse/PHOENIX-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-3061:
----------------------------------
Attachment: PHOENIX-3061_addendum4.patch
It seems that our async index building requires the test to run in it's own
mini cluster. Not sure why this is - I'll open a separate JIRA for this, but
it's not a blocker.
I'll commit this version which will hopefully pass...
> 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
> Assignee: Tongzhou Wang
> Priority: Blocker
> Labels: easyfix
> Fix For: 4.8.0
>
> Attachments: PHOENIX-3061_addendum2.patch,
> PHOENIX-3061_addendum3.patch, PHOENIX-3061_addendum4.patch, fix.diff
>
>
> 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)
