You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2018/08/01 06:24:47 UTC
[jira] [Issue Comment Deleted] (HBASE-20521)
TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script
run fail
[ https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated HBASE-20521:
--------------------------
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> 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)