[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-09 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468768#comment-16468768
 ] 

Hudson commented on HBASE-20521:


Results for branch master
[build #325 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/325/]: (x) 
*{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/325//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/325//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/325//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> 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)

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-09 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468692#comment-16468692
 ] 

Hudson commented on HBASE-20521:


Results for branch branch-2.0
[build #277 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/277/]: 
(/) *{color:green}+1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/277//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/277//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/277//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> 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)

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-09 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468677#comment-16468677
 ] 

Hudson commented on HBASE-20521:


Results for branch branch-2
[build #713 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/713/]: 
(x) *{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/713//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/713//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/713//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> 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)

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-08 Thread Mike Drob (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468273#comment-16468273
 ] 

Mike Drob commented on HBASE-20521:
---

Thank you for catching that, [~openinx]. Pushed revert and recommit to 
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)

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-08 Thread Michael Jin (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468266#comment-16468266
 ] 

Michael Jin commented on HBASE-20521:
-

Got it, thanks!

> 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)

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-08 Thread Zheng Hu (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468264#comment-16468264
 ] 

Zheng Hu commented on HBASE-20521:
--

Not necessary, can just revert and commit the patch with jira number... I can 
handle this later.

> 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)

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-08 Thread Michael Jin (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468255#comment-16468255
 ] 

Michael Jin commented on HBASE-20521:
-

[~openinx], should I submit a new patch? 

> 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)

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-08 Thread Zheng Hu (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468250#comment-16468250
 ] 

Zheng Hu commented on HBASE-20521:
--

[~menjin], [~mdrob], you missed the jira number in your patch, please revert 
it, and commit again ... 

https://github.com/apache/hbase/commit/b748ea3b0d3a074b976fa0ae59fc591303e805a0

> 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)

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-07 Thread Michael Jin (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466698#comment-16466698
 ] 

Michael Jin commented on HBASE-20521:
-

Ted, Mike, thanks!

> 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)

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-07 Thread Ted Yu (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466525#comment-16466525
 ] 

Ted Yu commented on HBASE-20521:


Mike - take your time, please merge tomorrow.

> 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)

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-07 Thread Mike Drob (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-07 Thread Michael Jin (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465586#comment-16465586
 ] 

Michael Jin commented on HBASE-20521:
-

[~mdrob], any update about the attach?

> 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)

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-03 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463368#comment-16463368
 ] 

Hadoop QA commented on HBASE-20521:
---

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
16s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 1 new or modified test 
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
23s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  5m 
 5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
43s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
58s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  1m 
26s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green}  0m 
53s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
14s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} scalac {color} | {color:green}  1m 
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  5m 
 2s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
17m  5s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m 
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green}  1m  
5s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 16m 
21s{color} | {color:green} hbase-mapreduce in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  5m  
8s{color} | {color:green} hbase-spark in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
28s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 71m 49s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:d8b550f |
| JIRA Issue | HBASE-20521 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12921886/HBASE-20521.master.002.patch
 |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  shadedjars  
hadoopcheck  hbaseanti  checkstyle  compile  scalac  scaladoc  |
| uname | Linux

[jira] [Commented] (HBASE-20521) TableOutputFormat.checkOutputSpecs conf checking sequence cause pig script run fail

2018-05-03 Thread Michael Jin (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463243#comment-16463243
 ] 

Michael Jin commented on HBASE-20521:
-

[~mdrob], just attached a patch, include code change and unit test, please help 
to review yourself or invite other reviewer, looks a little bit odd put 
"hbase-mapreduce" module function test under "hbase-spark", but create spark 
env and hbase env("TEST_UTIL" class) really a great help.

> 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-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)