You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/12 00:00:21 UTC
[jira] [Resolved] (HBASE-8722) Specify and document the FileSystem level behaviors required by HBase
[ https://issues.apache.org/jira/browse/HBASE-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell resolved HBASE-8722.
----------------------------------------
Resolution: Not A Problem
> Specify and document the FileSystem level behaviors required by HBase
> ---------------------------------------------------------------------
>
> Key: HBASE-8722
> URL: https://issues.apache.org/jira/browse/HBASE-8722
> Project: HBase
> Issue Type: Umbrella
> Reporter: Andrew Kyle Purtell
> Priority: Major
>
> HADOOP-9361 is an umbrella for an effort to strictly define the expected behavior of filesystem APIs, and then write tests to verify compliance. Currently we implicitly require some HDFS semantics that may not be available in other filesystems or data storage options. We should specify and document the filesystem level behaviors expected by HBase so they are visible as part of this effort. Then filesystem providers can know what is required for HBase application support through spec and standalone tests and won't need to bootstrap a full HBase installation, which can be a complex and error-prone undertaking if the semantics of the underlying storage are incompatible.
> Some areas that come to mind are: close-to-open, pread, lease recovery, flush/sync, atomic renames.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)