You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/12/04 14:58:00 UTC

[jira] [Commented] (HADOOP-14112) Über-jira adl:// Azure Data Lake Phase I: Stabilization

    [ https://issues.apache.org/jira/browse/HADOOP-14112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276896#comment-16276896 ] 

Steve Loughran commented on HADOOP-14112:
-----------------------------------------

Are all these things in 2.9 and 3.0? If so, let's move the rest to phase II and close this one

> Über-jira adl:// Azure Data Lake Phase I: Stabilization
> -------------------------------------------------------
>
>                 Key: HADOOP-14112
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14112
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/adl
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Steve Loughran
>            Assignee: John Zhuge
>
> Uber JIRA to track things needed for Azure Data Lake to be considered stable and adl:// ready for wide use.
> Based on the experience with other object stores, the things which usually surface once a stabilizing FS is picked up and used are
> * handling of many GB files, up and down, be it: efficiency of read, when the writes take place, file leakage, time for close() and filesystem shutdown
> * resilience to transient failures
> * reporting of problems/diagnostics
> * security option tuning
> * race conditions
> * differences between implementation and what actual applications expect



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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