[
https://issues.apache.org/jira/browse/HBASE-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HBASE-4510:
---------------------------
Priority: Major (was: Blocker)
Summary: Check and workaround usage of internal HDFS APIs in HBase (was:
HDFS-1620 related changes downstream (For compiling with HDFS 0.23+))
Unfortunately my vacation's made me go way off-sync surrounding this issue.
Todd has fixed build for 0.23 via HDFS-2412 already, and that patch would be
available for 0.23 at least (graceful deprecation being the plan).
We're proposing adding a public 'check' of SafeMode status in HDFS upstream,
via HDFS-2413, which HBASE and other projects can then rely on.
Changes made to ticket:
- Changed title to reflect new goal.
- Changed the severity down from blocker as it isn't anymore, after HDFS-2412
went in.
> Check and workaround usage of internal HDFS APIs in HBase
> ---------------------------------------------------------
>
> Key: HBASE-4510
> URL: https://issues.apache.org/jira/browse/HBASE-4510
> Project: HBase
> Issue Type: Task
> Affects Versions: 0.94.0
> Reporter: Harsh J
> Assignee: Harsh J
>
> HBase isn't seemingly compiling anymore on 0.23 after the HDFS-1620 naming
> refactorings were carried out.
> Two solutions:
> * We use new classnames. This breaks HBase's backward compatibility with
> older Hadoop releases (is that a concern with future releases?)
> * HBase gets its own sets of constants as the upstream one is not marked for
> public usage. This needs a little more maintenance on HBases' side.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
