[
https://issues.apache.org/jira/browse/HBASE-12422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246291#comment-14246291
]
stack commented on HBASE-12422:
-------------------------------
Sorry the patch is big but its big because I added timeouts to TestHBaseFsck
and to TestLoadIncrementalHFilesSplitRecovery so they wouldn't go zombie on us
anymore when an issue. Other changes in TestLoadIncrementalHFilesSplitRecovery
are refactorings so we reuse a connection rather than use deprecated HTable
constructor; ditto in LoadIncrementalHFiles (this latter and similar change in
TestHBaseFsck) fixed the failing tests). The change in HBaseFsck just moves us
onto newer Interfaces. Then there is Solomon's original change.
> Use ConnectionFactory in HTable constructors
> --------------------------------------------
>
> Key: HBASE-12422
> URL: https://issues.apache.org/jira/browse/HBASE-12422
> Project: HBase
> Issue Type: Bug
> Components: Client
> Reporter: Solomon Duskis
> Assignee: stack
> Priority: Minor
> Fix For: 1.0.0, 2.0.0
>
> Attachments: 12422v2.txt, 12422v3.txt, 12422v4.txt, 12422v5.txt,
> HBASE-12422.patch, HBASE-12422.patch, HBASE-12422.patch, HBASE-12422.patch,
> HBASE-12422.patch
>
>
> Use ConnectionFactory in HTable instead of ConnectionManager.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
