[
https://issues.apache.org/jira/browse/HADOOP-17981?focusedWorklogId=674006&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-674006
]
ASF GitHub Bot logged work on HADOOP-17981:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 02/Nov/21 21:29
Start Date: 02/Nov/21 21:29
Worklog Time Spent: 10m
Work Description: steveloughran opened a new pull request #3611:
URL: https://github.com/apache/hadoop/pull/3611
Compared to #3597 this moves the recovery handling into
the application code.
However, the nominally simpler "fs api" strategy had actually got more
complicated with
interfaces in RawLocalFS for testing, etc etc, and the hive team were
showing a dangerous amount of interest and using the same API,
judging by the comments.
This solution at one new interface in hadoop fs, which is straight forward
it to declare
stable as s3 and abfs and others can all serve this field up immediately.
With the interface and part capabilities probes, anything is free to use
this for:
Tracking changes across files, verifying that objects are unchanged
and this special case of resilience recovery.
What else do we need?
We would like, but don't need, an option for abfs to
throw meaningful exceptions on rename failures
and for it not to attempt to use modtimes to recover from
source file not found events.
### For code changes:
- [X] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 674006)
Time Spent: 4h 10m (was: 4h)
> Support etag-assisted renames in FileOutputCommitter
> ----------------------------------------------------
>
> Key: HADOOP-17981
> URL: https://issues.apache.org/jira/browse/HADOOP-17981
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs, fs/azure
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> To deal with some throttling/retry issues in object stores,
> pass the FileStatus entries retrieved during listing
> into a private interface ResilientCommitByRename which filesystems
> may implement to use extra attributes in the listing (etag, version)
> to constrain and validate the operation.
> Although targeting azure, GCS and others could use. no point in S3A as they
> shouldn't use this committer.
> # And we are not going to do any changes to FileSystem as there are explicit
> guarantees of public use and stability.
> I am not going to make that change as the hive thing that will suddenly start
> expecting it to work forever.
> # I'm not planning to merge this in, as the manifest committer is going to
> include this and more (MAPREDUCE-7341)
> However, I do need to get this in on a branch, so am doing this work on trunk
> for dev & test and for others to review
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
