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

Hudson commented on HBASE-21273:
--------------------------------

Results for branch master
        [build #533 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/533/]: (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/533//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/533//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/533//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


(/) {color:green}+1 client integration test{color}


> Move classes out of org.apache.spark namespace
> ----------------------------------------------
>
>                 Key: HBASE-21273
>                 URL: https://issues.apache.org/jira/browse/HBASE-21273
>             Project: HBase
>          Issue Type: Task
>          Components: spark
>    Affects Versions: 3.0.0
>            Reporter: Mike Drob
>            Assignee: Mike Drob
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HBASE-21273.master.001.patch
>
>
> We currently have classes in the org.apache.spark space, I expect the Spark 
> PMC would be upset with us if we started releasing those. Let's see if we can 
> move them out.
> There's an ancient (2016) comment saying we need them there for access 
> restriction reasons, if that's the case then we'll have to work through that 
> issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to