[
https://issues.apache.org/jira/browse/HADOOP-19795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18067958#comment-18067958
]
ASF GitHub Bot commented on HADOOP-19795:
-----------------------------------------
manika137 commented on PR #8212:
URL: https://github.com/apache/hadoop/pull/8212#issuecomment-4116533878
> * Document that it means that if the file isn't found, there isn't a
failure until the first read.
> * Make sure that openFile() builder code does this too if no status (or
the wrong status type) is passed in, and do it _automatically_. That filesystem
api spec says "existence checks may be delayed".
Sure. Will ensure functionality for all edge cases including file not found
with wrong filestatus type or without filestatus. Will document the expectation.
> ABFS: GetPathStatus Optimization on OpenFileForRead
> ---------------------------------------------------
>
> Key: HADOOP-19795
> URL: https://issues.apache.org/jira/browse/HADOOP-19795
> Project: Hadoop Common
> Issue Type: Task
> Components: fs/azure
> Affects Versions: 3.4.1, 3.4.2
> Reporter: Manika Joshi
> Assignee: Manika Joshi
> Priority: Major
> Labels: pull-request-available
>
> We do a getPathStatus call during file open for read. This call is primarily
> used to fetch the file’s metadata properties before the actual read begins.
> We are now introducing an optional, config-driven read flow that avoids the
> getPathStatus call during open and instead derives required metadata from the
> read response itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
