hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15875) Remove HTable references and HTableInterface
Date Tue, 31 May 2016 02:56:12 GMT

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

stack commented on HBASE-15875:

[~appy] Is it possible that we are dropping an 'excludes' in the top level of a build? See
the report here: https://builds.apache.org/job/PreCommit-HBASE-Build/2054/artifact/patchprocess/patch-asflicense-problems.txt

> Remove HTable references and HTableInterface
> --------------------------------------------
>                 Key: HBASE-15875
>                 URL: https://issues.apache.org/jira/browse/HBASE-15875
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jurriaan Mous
>            Assignee: Jurriaan Mous
>         Attachments: HBASE-15875.patch, HBASE-15875.v1.patch, HBASE-15875.v2.patch
> I want to add a new AsyncTable implementation and to do that with great quality I want
to run all the tests with a sync Table implementation which uses the AsyncTable within. To
do this the HbaseTestingUtility has to return Table instead of HTable.
> I saw this as the ideal opportunity to remove all deprecated HTableInterface methods
in 2.0 branch and thus the interface itself. This means all auto flush settings are removed.
> Some discussion points:
> * I had to remove doBulkLoad(Path hfofDir, final HTable table) from LoadIncrementalHFiles
because of the hard HTable usage and replaced usages to the other doBulkLoad(Path hfofDir,
final Admin admin, Table table, RegionLocator regionLocator) method.
> * HBaseTestingUtility now returns Table instead of HTable
> * I removed all the methods from HConnection that were also in Connection + I removed
the getTable methods which should not be used anymore. (HConnection is deprecated so could
be removed itself)

This message was sent by Atlassian JIRA

View raw message