-
Notifications
You must be signed in to change notification settings - Fork 3k
Docs: Add S3 delete tagging docs #4443
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
Docs: Add S3 delete tagging docs #4443
Conversation
37cc133 to
b3c0a10
Compare
b3c0a10 to
0284519
Compare
singhpk234
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.
Thanks @rajarshisarkar for this change !!!
d42e4f2 to
6ec115a
Compare
singhpk234
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.
LGTM @rajarshisarkar !!!, just a question on soft-delete
6ec115a to
64adb47
Compare
64adb47 to
93420b4
Compare
docs/integrations/aws.md
Outdated
| ### S3 Delete | ||
|
|
||
| When the catalog property `s3.delete-enabled` is set to `false`, the objects are not deleted from S3. | ||
| This is set to `true` by default. |
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.
we should link to the next section with something in the line of "This is expected to be used in combination with s3 delete tagging", so objects are tagged and removed using S3 lifecycle policy. See xxx (link to next section) for more details".
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.
Actually, given that the delete-enabled is only relevant under the context of tagging, would it make more sense to just mention this in the tagging section below, instead of having its own section?
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.
Makes sense to me. I have made the changes.
712e10b to
88af363
Compare
88af363 to
4d599b0
Compare
|
This isn't a comment about this PR specifically but the content in the aws.md file feels like a collection of many unrelated things under the AWS umbrella. Maybe we should start thinking about how to break this up, such as moving the S3 docs to a FileIO section, move the Spark material somewhere in the Spark section, etc. |
|
Thanks, for the inputs @samredai ! @jackye1995 Please let me know your thoughts on the scope of improvement for |
jackye1995
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.
Thanks for the work!
|
I have a PR for consolidating configurations, it might be good to add these properties there like |
|
@samredai Yeah, makes sense to me. |
This PR add docs for #4342
cc: @rdblue @danielcweeks @jackye1995 @arminnajafi @singhpk234 @amogh-jahagirdar @xiaoxuandev @yyanyy