[ 
https://issues.apache.org/jira/browse/HADOOP-14837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846883#comment-17846883
 ] 

ASF GitHub Bot commented on HADOOP-14837:
-----------------------------------------

bpahuja commented on PR #6407:
URL: https://github.com/apache/hadoop/pull/6407#issuecomment-2114600740

   @steveloughran , I have pushed the changes for 
`ITestS3AReadRestoredGlacierObjects.java` , and it now has only 1 test with all 
the test cases. In total , the setup happens twice, once for Glacier Storage 
class and once more for Glacier Deep Archive Storage class. The number of 
setups happening has been reduced , where earlier it created the file for each 
test case. 
   Please review whenever you get some time. 
   Let me know if any more changes are needed here. 
   
   
   Thanks :) 




> 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]

Reply via email to