[
https://issues.apache.org/jira/browse/HADOOP-17199?focusedWorklogId=478706&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-478706
]
ASF GitHub Bot logged work on HADOOP-17199:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Sep/20 17:24
Start Date: 03/Sep/20 17:24
Worklog Time Spent: 10m
Work Description: steveloughran commented on pull request #2269:
URL: https://github.com/apache/hadoop/pull/2269#issuecomment-686638484
ok, all as good as it gets. Will apply the patch filtering out whitespace.
----------------------------------------------------------------
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: 478706)
Time Spent: 1h 40m (was: 1.5h)
> Backport HADOOP-13230 list/getFileStatus changes for preserved directory
> markers to 3.2.x
> -----------------------------------------------------------------------------------------
>
> Key: HADOOP-17199
> URL: https://issues.apache.org/jira/browse/HADOOP-17199
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.2.1, 3.1.3
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.2.2
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Our supported Hadoop releases all need to handle s3a stores where the s3a
> client does not delete directory markers.
> This is only the minimal set of list changes; no intent of changing marker
> retention policy. It should be transparent to all clients
> * list/getFileStatus changes
> * backwards compatible test of new algorithm
> * new tests to verify marker handling
> * marker rename bug (HADOOP-17200) surfacing in testing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
