[
https://issues.apache.org/jira/browse/HADOOP-14837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17820759#comment-17820759
]
ASF GitHub Bot commented on HADOOP-14837:
-----------------------------------------
steveloughran commented on PR #6407:
URL: https://github.com/apache/hadoop/pull/6407#issuecomment-1964529624
I'm doing nothing but helping it get Hadoop 3.4.0 out the door this week. No
code of my except related to packaging; no reviews of other people except
related to the release at all. Sorry.
Well you are waiting for a review on your code from myself or someone else
-why not getting involved? There is no release engineering team doing this and
it is up to all of us developers in the community to get our hands dirty. We
all have different deployment environments and we all have different things we
want to test. And, given this is the first public release with the AWS V2 SDK:
it matters a lot that this thing ships. It will be the way we actually find
real world bugs.
Look on the hadoop common-dev list for the announcement of the next release
candidate: once the announcement is made we have five days to test and vote on
the RC. That is why we are under so much time pressure here.
Note I've created a project,
https://github.com/apache/hadoop-release-support , to assist in qualifying. One
thing which would be good it would be some extra scripts we could run to help
validate storage operations -operations which we can then execute against cloud
storage from either the local host or a remote one -I am qualifying the Arm64
build on a raspberry pi5 under my television and would like to have that
testing fully automated.
Anything you can do here will be very much appreciated. And like I said: I'm
unlikely to be looking at any other code right now.
> Handle S3A "glacier" data
> -------------------------
>
> Key: HADOOP-14837
> URL: https://issues.apache.org/jira/browse/HADOOP-14837
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.0.0-beta1
> Reporter: Steve Loughran
> Assignee: Bhavay Pahuja
> Priority: Minor
> Labels: pull-request-available
>
> SPARK-21797 covers how if you have AWS S3 set to copy some files to glacier,
> they appear in the listing but GETs fail, and so does everything else
> We should think about how best to handle this.
> # report better
> # if listings can identify files which are glaciated then maybe we could have
> an option to filter them out
> # test & see what happens
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
