[
https://issues.apache.org/jira/browse/HADOOP-16202?focusedWorklogId=536834&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-536834
]
ASF GitHub Bot logged work on HADOOP-16202:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jan/21 17:17
Start Date: 16/Jan/21 17:17
Worklog Time Spent: 10m
Work Description: ThomasMarquardt commented on pull request #2584:
URL: https://github.com/apache/hadoop/pull/2584#issuecomment-761600086
OK, so must() has already shipped, in that case sure, it should stay. I
still have a question. If I pass an option via must(), can it be ignored by
the implementation? I read your documentation, specifically, "This means that
it is not a requirement for the stores to actually read the the read policy or
file length values and use them when opening files." To me, this says that
options passed via must() can be ignored. If this is true, then what is the
difference between must() and opt()? Is it that must() can result in an
unsupported exception, but opt() never results in an unsupported exception?
----------------------------------------------------------------
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: 536834)
Time Spent: 8.5h (was: 8h 20m)
> Stabilize openFile() and adopt internally
> -----------------------------------------
>
> Key: HADOOP-16202
> URL: https://issues.apache.org/jira/browse/HADOOP-16202
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs, fs/s3, tools/distcp
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Time Spent: 8.5h
> Remaining Estimate: 0h
>
> The {{openFile()}} builder API lets us add new options when reading a file
> Add an option {{"fs.s3a.open.option.length"}} which takes a long and allows
> the length of the file to be declared. If set, *no check for the existence of
> the file is issued when opening the file*
> Also: withFileStatus() to take any FileStatus implementation, rather than
> only S3AFileStatus -and not check that the path matches the path being
> opened. Needed to support viewFS-style wrapping and mounting.
> and Adopt where appropriate to stop clusters with S3A reads switched to
> random IO from killing download/localization
> * fs shell copyToLocal
> * distcp
> * IOUtils.copy
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
