-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-17483. Remove option to enable/disable S3A magic committer . It is always on #2637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HADOOP-17483. Remove option to enable/disable S3A magic committer . It is always on #2637
Conversation
|
💔 -1 overall
This message was automatically generated. |
liuml07
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unit tests seem fine. +1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deprecate this method as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
|
I was thinking about this a bit more and worrying about "maybe I should leave the switch in but true everywhere and only document in minimal terms" Why so? Because it is doing something unusual: renaming paths. If anyone ever tried to do a distcp from, say, hdfs and there were __magic paths in there, they'd trigger the behaviour. With a switch to turn it off for those operations, at least if someone complains that we are doing bad things. Note: given the hdfs rule that _ is the temp prefix I'm not over-worried, but I just think it may be good to have an emergency way to unwind |
Change-Id: I9f31b531d637fb0da6f9cdd207e9628e7dcf5e88
3eb9209 to
53ebce8
Compare
|
💔 -1 overall
This message was automatically generated. |
|
Yes, this extra care is good to have I think. |
|
I agree. I will switch to on, leave the ability to disable off, and change in docs "how to disable" and explain what it means/why. I'll make a separate PR as it's very different from this one |
|
Closing, superceded by #2656 |
#2636 updated the docs; this is the code-side change to remove the option of disabling magic committer support in the FS
That was a safety check to stop people enabling it on inconsistent/unguarded buckets. We can stop worrying there.
Before anyone asks: what about inconsistent third party stores: every one else's has always been consistent.
tested: s3 london with
-Dparallel-tests -DtestsThreadCount=6 -Dmarkers=delete -Dtest=no -Dfs.s3a.directory.marker.audit=true -DscaleLooks like I skipped the unit tests there...lets see what yetus says