Details
Description
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
Attachments
Issue Links
- is cloned by
-
HADOOP-14764 Über-jira adl:// Azure Data Lake Phase II: Performance, Resilience and Testing
-
- Resolved
-
1.
|
review ADL Docs |
|
Resolved | Steve Loughran |
2.
|
Rename ADLS credential properties |
|
Resolved | John Zhuge |
3.
|
ADL module has messed doc structure |
|
Resolved | Mingliang Liu |
4.
|
Remove misplaced ADL service provider config file for FileSystem |
|
Resolved | John Zhuge |
5.
|
Remove unused AdlConfKeys#ADL_EVENTS_TRACKING_SOURCE |
|
Resolved | John Zhuge |
6.
|
Set default ADLS access token provider type to ClientCredential |
|
Resolved | John Zhuge |
7.
|
Azure Data Lake doc is missing required config entry |
|
Resolved | Atul Sikaria |
8.
|
Fix ADLS doc for credential provider |
|
Resolved | John Zhuge |
9.
|
TestAdlFileSystemContractLive fails to clean up |
|
Resolved | John Zhuge |
10.
|
Add ADLS sensitive config keys to default list |
|
Resolved | John Zhuge |
11.
|
Rename ADLS CONTRACT_ENABLE_KEY |
|
Resolved | Mingliang Liu |
12.
|
Make ADLS doc of setting up client key up to date |
|
Resolved | John Zhuge |
13.
|
AdlFilesystem#initialize swallows exception when getting user name |
|
Resolved | John Zhuge |