[jira] [Updated] (HBASE-21273) Move classes out of org.apache.spark namespace
[ https://issues.apache.org/jira/browse/HBASE-21273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-21273: Fix Version/s: connector-1.0.0 Component/s: hbase-connectors > 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: hbase-connectors, spark >Affects Versions: 3.0.0 >Reporter: Mike Drob >Assignee: Mike Drob >Priority: Major > Fix For: 3.0.0, connector-1.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)
[jira] [Updated] (HBASE-21273) Move classes out of org.apache.spark namespace
[ https://issues.apache.org/jira/browse/HBASE-21273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated HBASE-21273: -- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for review, Ted. Pushed to master. > 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)
[jira] [Updated] (HBASE-21273) Move classes out of org.apache.spark namespace
[ https://issues.apache.org/jira/browse/HBASE-21273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated HBASE-21273: -- Status: Patch Available (was: Open) Let's see if automated testing finds any issue with this. > 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)
[jira] [Updated] (HBASE-21273) Move classes out of org.apache.spark namespace
[ https://issues.apache.org/jira/browse/HBASE-21273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated HBASE-21273: -- Attachment: HBASE-21273.master.001.patch > 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)