[
https://issues.apache.org/jira/browse/HBASE-14676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972197#comment-14972197
]
Jonathan Hsieh commented on HBASE-14676:
----------------------------------------
I think we need a name different from RegionTable. Here's a few suggestions:
* RegionAsTable
* RegionToTable
* RegionToTableAdapter
Does closing the regionscanner inside RegionScannerToResultScannerAdaptor make
sense?
Any reason why checkAndPut/checkAndDelete/ICV/checkAndMutate were skipped?
Implement, add a todo, or add reason why?
> HBaseTestCase clean out: Purge Incommon Interface and Table and Region
> implementations
> --------------------------------------------------------------------------------------
>
> Key: HBASE-14676
> URL: https://issues.apache.org/jira/browse/HBASE-14676
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Attachments: 14676.patch, 14676v2.txt, 14676v3.txt, RegionAdmin.java
>
>
> As part of the hollowing out of the old HBaseTestCase in preparation for
> removal, this patch purges the old Incommon trick that made it so you could
> pass an Interface to a method to do loading or testing and the implementation
> could be an HTable or a Region. Instead, replace it with a RegionTable, a
> Regoin that has the Table Interface as a decoration so you can use same
> loading code and same test both on top of the Region or on other side of
> network via HTable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
