[
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466515#comment-16466515
]
Mike Drob commented on HBASE-20521:
-----------------------------------
minor nit: you lost a space between if and opening parenthesis in
TableOutputFormat. I (or somebody else) can fix this on commit.
I ran the patch and also tested it against my pig script and it looks like
things work. Ran the unit test against a version that only uses getConf() and
doesn't read the context conf and it failed as expected. So we're good on that
side.
[~tedyu] - if you have no further comments on RB feel free to push, otherwise
I'll pick this up tomorrow. Would like to see it in master, branch-2, and
branch-2.0
> TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script
> run fail
> -----------------------------------------------------------------------------------
>
> Key: HBASE-20521
> URL: https://issues.apache.org/jira/browse/HBASE-20521
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Affects Versions: 2.0.0
> Environment: spark 2.2.1, hbase 2.0.0
> Reporter: Michael Jin
> Assignee: Michael Jin
> Priority: Major
> Fix For: 3.0.0, 2.1.0, 2.0.1
>
> Attachments: HBASE-20521.master.001.patch,
> HBASE-20521.master.002.patch
>
>
> HBASE-20295 fix null point exception of "conf" member variable, add
> "context.getConfiguration()" in case when "conf" object was not been properly
> initialized, and put it into the first priority checking sequence, this code
> change affect user call "setConf" explicitly initialize "conf" object in
> TableOutputFormat object, proposal to change checking sequence, use "conf"
> object from "getConf" method first .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)