hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-15691) Add PathCapabilities to FS and FC to complement StreamCapabilities
Date Thu, 10 Jan 2019 17:09:01 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-15691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Steve Loughran updated HADOOP-15691:
    Status: Patch Available  (was: Open)

HADOOP-15691 patch 004
* applies to trunk
* adds a probe  for DT support. Base impl calls getCanonicalServiceName() for this; subclasses
which do support DTs shuld really do a faster check
* moved arg validation into its own org.apache.hadoop.fs.impl.PathCapabilitiesSupport helper;
easier for subclasses and FC to user
* moved FsLinkResolution to fs.impl. package too
* Azure ABFS capabilities exported, dynamcially built up from state of the instance.

No tests of DT support, im afraid.

Cloud infras tested against: none

> Add PathCapabilities to FS and FC to complement StreamCapabilities
> ------------------------------------------------------------------
>                 Key: HADOOP-15691
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15691
>             Project: Hadoop Common
>          Issue Type: New Feature
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>         Attachments: HADOOP-15691-001.patch, HADOOP-15691-002.patch, HADOOP-15691-003.patch,
> Add a {{PathCapabilities}} interface to both FileSystem and FileContext to declare the
capabilities under the path of an FS
> This is needed for 
> * HADOOP-14707: declare that a dest FS supports permissions
> * object stores to declare that they offer PUT-in-place alongside (slow-rename)
> * Anything else where the implementation semantics of an FS is so different caller apps
would benefit from probing for the underlying semantics
> I know, we want all filesystem to work *exactly* the same. But it doesn't hold, especially
for object stores —and to efficiently use them, callers need to be able to ask for specific

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message