[
https://issues.apache.org/jira/browse/PHOENIX-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762364#comment-16762364
]
Hudson commented on PHOENIX-5111:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #321 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/321/])
PHOENIX-5111: Null Pointer exception fix in index tool due to outputpath
(gjacoby: rev c8f44549a0401283d4147413f2c36afa0cd7a9f6)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexTool.java
> IndexTool gives NPE when trying to do a direct build without an output-path
> set
> -------------------------------------------------------------------------------
>
> Key: PHOENIX-5111
> URL: https://issues.apache.org/jira/browse/PHOENIX-5111
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.1
> Reporter: Geoffrey Jacoby
> Assignee: Gokcen Iskender
> Priority: Minor
> Fix For: 4.15.0, 5.1.0
>
> Attachments: PHOENIX-5111.patch, PHOENIX-5111.patch
>
>
> The IndexTool has several modes. If the -direct or -partial-rebuild flags are
> not set, the tool assumes the user wants to rebuild the index by creating
> HFiles and then bulk-loading them back into HBase, and requires an extra
> -output-path flag to deterine where the temporary HFiles should live.
> In practice, we've found that -direct mode (which loads using HBase Puts) is
> quicker. However, even though there's logic to not require the -output-path
> flag when -direct mode is chosen, the IndexTool will throw an NPE if it's not
> present.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
