hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13126) Clean up API for unintended methods within non-private classes.
Date Tue, 17 Mar 2015 00:07:38 GMT

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

Mikhail Antonov commented on HBASE-13126:


bq. +1. Curious what would be the practical impact of moving a class from hbase-server-test
to hbase-server. Both have to be on the classpath already in order for tests to work, or as
you mention, hbase-testing-util does the aggregation. Strictly speaking moving a class from
one jar to another is a binary change incompatible on some level though.

I guess majority of folks directly using HBase minicluster are Phoenix/Hive (opentsdb?) and
other similar downstream projects, so maybe we could look at some of them we can think of,
and see if they would be hurt?

> Clean up API for unintended methods within non-private classes.
> ---------------------------------------------------------------
>                 Key: HBASE-13126
>                 URL: https://issues.apache.org/jira/browse/HBASE-13126
>             Project: HBase
>          Issue Type: Task
>          Components: API
>    Affects Versions: 2.0.0
>            Reporter: Sean Busbey
>            Priority: Blocker
>             Fix For: 2.0.0
> Over in the review for HBASE-12972, [~enis] mentioned that one of the HBTU methods wasn't
intended for public consumption.
> Can we build a list of such methods across the API, appropriately annotate them for 2.0,
and deprecate them in earlier versions with a warning that they're going to be restricted?

This message was sent by Atlassian JIRA

View raw message