[
https://issues.apache.org/jira/browse/HADOOP-17323?focusedWorklogId=514504&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-514504
]
ASF GitHub Bot logged work on HADOOP-17323:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 20/Nov/20 08:26
Start Date: 20/Nov/20 08:26
Worklog Time Spent: 10m
Work Description: mukund-thakur commented on pull request #2479:
URL: https://github.com/apache/hadoop/pull/2479#issuecomment-731021298
CC @steveloughran Do check during your review session.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 514504)
Time Spent: 20m (was: 10m)
> s3a getFileStatus("/") to skip IO
> ---------------------------------
>
> Key: HADOOP-17323
> URL: https://issues.apache.org/jira/browse/HADOOP-17323
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Assignee: Mukund Thakur
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Calls to "hadoop fs ls s3a://something/" add a full getFileStatus() sequence
> (HEAD, LIST, LIST) because FsShell Ls calls getFileStatus on every input.
> We should just build a root status entry immediately. There's one
> consequence: if a user has disabled the s3a existence probe, there will be no
> checks for the bucket existence. But that can be viewed as a "well, that's
> what happens" behaviour
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
