hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Purtell <apurt...@apache.org>
Subject Re: Removing hbase-native-client (HBASE-19419)
Date Mon, 04 Dec 2017 23:44:13 GMT
Thanks for the feedback. I intend to commit HBASE-19419 shortly unless
objection.

On Mon, Dec 4, 2017 at 3:38 PM, Ted Yu <yuzhihong@gmail.com> wrote:

> +1 on removing pre-HBASE-14850
> <https://issues.apache.org/jira/browse/HBASE-14850> stuff.
>
> On Mon, Dec 4, 2017 at 3:28 PM, Josh Elser <elserj@apache.org> wrote:
>
> > Makes sense to me.
> >
> > *soapbox* I think focusing on https://issues.apache.org/jira
> > /browse/HBASE-14850 would be a better use of time than trying to
> > revitalize the old stuff (which I assume has begun to rot).
> >
> >
> > On 12/4/17 3:00 PM, Andrew Purtell wrote:
> >
> >> Mike Drob pointed me at HBASE-19176, where hbase-native-client has
> already
> >> been removed from branch-2 given a similar rationale. Therefore I intend
> >> to
> >> do the same for branch-1.4 and branch-1. On HBASE-19419 Mike asked if
> >> hbase-native-client would be removed from branch-1.1, branch-1.2, and
> >> branch-1.3 as well. I can do that, but would like to hear from the
> >> respective branch RMs if possible first.
> >>
> >> On Mon, Dec 4, 2017 at 11:43 AM, Andrew Purtell <apurtell@apache.org>
> >> wrote:
> >>
> >> We had a recent non-binding veto in a release candidate vote (for
> 1.1.13)
> >>> due to, I think, legitimate confusion over the status of the
> >>> hbase-native-client subdirectory in our source tree. This is a self
> >>> contained native code connector that is not hooked up to our Maven
> build.
> >>> Therefore there isn't an automated way for our RMs to produce binary
> >>> convenience artifacts that include this component. I'm not even sure it
> >>> is
> >>> buildable or functional at this point. It has not been updated for two
> >>> years.
> >>>
> >>> Because it is self contained, and in what appears to be an unmaintained
> >>> state, I would like to remove it for the 1.4.0 release, therefore from
> >>> branch-1.4 and up. Dropping it doesn't represent a compatibility
> problem
> >>> in
> >>> my view as it isn't hooked up to the build and seems unlikely anyone is
> >>> depending on it given we haven't had a single change nor issue reported
> >>> against it for two years.
> >>>
> >>> If someone does care about this, it can be resurrected at any time as
> an
> >>> independent GitHub based project.
> >>>
> >>> --
> >>> Best regards,
> >>> Andrew
> >>>
> >>> Words like orphans lost among the crosstalk, meaning torn from truth's
> >>> decrepit hands
> >>>     - A23, Crosstalk
> >>>
> >>>
> >>
> >>
> >>
>



-- 
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message