Skip to content
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

Add diagnostic logging for TrinoS3FileSystem delete #18494

Conversation

findepi
Copy link
Member

@findepi findepi commented Aug 2, 2023

No description provided.

@findepi findepi added the no-release-notes This pull request does not require release notes entry label Aug 2, 2023
@cla-bot cla-bot bot added the cla-signed label Aug 2, 2023
@@ -695,6 +697,7 @@ else if (deletePrefixResult == DeletePrefixResult.DELETE_KEYS_FAILURE) {
}
deleteObject(key + DIRECTORY_SUFFIX);
}
// TODO should we return true also when deleteObject() returned false? (currently deleteObject's return value is never used)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This behavior has been there for over 8 years now - see e0fe1c7
Maybe we should use the outcome of delete actually instead of simply returning true and offer to the users (temporarily for a few releases) a fallback setting to still return true independently of the returned result from S3 on deleting an object.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i don't want to decide this now in this PR. It's definitely difficult to change fragile things like this.

@findepi findepi merged commit 4ccd023 into trinodb:master Aug 7, 2023
@findepi findepi deleted the findepi/add-diagnostic-logging-for-trinos3filesystem-delete-bc5461 branch August 7, 2023 12:58
@github-actions github-actions bot added this to the 423 milestone Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed no-release-notes This pull request does not require release notes entry
Development

Successfully merging this pull request may close these issues.

3 participants