[
https://issues.apache.org/jira/browse/HBASE-9508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-9508:
-------------------------
Attachment: 9508.txt
In HRegionInfo, I restored getTableName so it took a byte array and added
getTable to get the TableName return.
In HTableDescriptor, added back remove(byte []). Looks like it was replaced by
remove(IBW).
Added back constructor to ClientScanner that used take tablename as byte array.
Also restored getTableName returning a byte array (added getTable if you want
TableName).
Added back an incrementColumnValue that takes a boolean for whether to write
the WAL -- have it call through to the override that specifes Durability.
In LoadIncrementalHFiles, added back override of tryAtomicRegionLoad that takes
a byte array for tablename.
In TableSplit added back overrides for constructors and methods that take table
name as byte array.
> Restore some API mistakenly removed in client, mapred*, and common
> ------------------------------------------------------------------
>
> Key: HBASE-9508
> URL: https://issues.apache.org/jira/browse/HBASE-9508
> Project: HBase
> Issue Type: Bug
> Components: Usability
> Reporter: stack
> Assignee: stack
> Priority: Critical
> Fix For: 0.98.0, 0.96.0
>
> Attachments: 9508.txt
>
>
> Here is contrib to the API compatibility story. I went over Aleks'
> compatibility report and restored removed or overriden methods and
> constructors, stuff that was in 0.94 non-deprecated and removed in 0.96.
> This patch is not comprehensive because some removals cannot be restored as
> in those that used take Writables (more on this later from Jon).
> The changes included here are mostly restore of methods that took a table
> name as a byte array replaced by a TableName object.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
