Skip to content

Conversation

@rajarshisarkar
Copy link
Contributor

@rajarshisarkar rajarshisarkar force-pushed the s3-delete-tagging-doc branch from b3c0a10 to 0284519 Compare April 4, 2022 10:28
Copy link
Contributor

@singhpk234 singhpk234 left a 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 !!!

@rajarshisarkar rajarshisarkar force-pushed the s3-delete-tagging-doc branch 3 times, most recently from d42e4f2 to 6ec115a Compare April 11, 2022 10:18
Copy link
Contributor

@singhpk234 singhpk234 left a 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

@rajarshisarkar rajarshisarkar force-pushed the s3-delete-tagging-doc branch from 6ec115a to 64adb47 Compare April 11, 2022 12:07
@rajarshisarkar rajarshisarkar force-pushed the s3-delete-tagging-doc branch from 64adb47 to 93420b4 Compare April 12, 2022 09:36
### 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.
Copy link
Contributor

@jackye1995 jackye1995 Apr 26, 2022

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".

Copy link
Contributor

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?

Copy link
Contributor Author

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.

@rajarshisarkar rajarshisarkar force-pushed the s3-delete-tagging-doc branch 2 times, most recently from 712e10b to 88af363 Compare April 26, 2022 08:29
@rajarshisarkar rajarshisarkar force-pushed the s3-delete-tagging-doc branch from 88af363 to 4d599b0 Compare April 26, 2022 08:57
@samredai
Copy link
Contributor

samredai commented May 4, 2022

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.

@rajarshisarkar
Copy link
Contributor Author

Thanks, for the inputs @samredai !

@jackye1995 Please let me know your thoughts on the scope of improvement for aws.md. We can create tasks accordingly.

Copy link
Contributor

@jackye1995 jackye1995 left a 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!

@jackye1995 jackye1995 merged commit 77b1e9b into apache:master May 24, 2022
@samredai
Copy link
Contributor

I have a PR for consolidating configurations, it might be good to add these properties there like spark.sql.catalog.<catalog>.s3.delete.tags.<key>: #4801

@rajarshisarkar
Copy link
Contributor Author

@samredai Yeah, makes sense to me.

@samredai
Copy link
Contributor

samredai commented May 26, 2022

Added to the configurations page PR: https://github.com/apache/iceberg/pull/4801/files#diff-947e999f40ea405c702496fc987ab2c322222d2488680be54ddfa3447c3569faR155-R158

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants