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

ARROW-17079: [C++] Improve error messages for AWS S3 calls #13979

Merged
merged 8 commits into from
Aug 30, 2022

Conversation

pcmoritz
Copy link
Contributor

@pcmoritz pcmoritz commented Aug 26, 2022

First part of improving error messages from S3 operations. We include the operation that failed in the error message now. This makes it easier to debug problems (e.g. bucket permissions or other infrastructure hickups) because it allows to re-run the operation that failed with the AWS CLI for further diagnosing what is going wrong.

Example (changes in bold):

When getting information for key 'test.csv' in bucket 'pcmoritz-test-bucket-arrow-errors': AWS Error [code 15] during HeadObject operation: No response body.

@github-actions
Copy link

@github-actions
Copy link

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

@kou kou changed the title ARROW-17079: Improve error messages for AWS S3 calls ARROW-17079: [C++] Improve error messages for AWS S3 calls Aug 26, 2022
@pcmoritz pcmoritz requested a review from pitrou August 26, 2022 07:45
@pcmoritz
Copy link
Contributor Author

@pitrou Do you want to have a look at / review this PR?

Copy link
Member

@pitrou pitrou left a comment

Choose a reason for hiding this comment

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

Nice improvement, thank you. Can you show an example error message?

@pcmoritz
Copy link
Contributor Author

pcmoritz commented Aug 29, 2022

Yes of course! For example for loading a dataset from s3://pcmoritz-test-bucket-arrow-errors/test.csv (the bucket has all access permissions revoked):

After (changes in bold):

When getting information for key 'test.csv' in bucket 'pcmoritz-test-bucket-arrow-errors': AWS Error [code 15] during HeadObject operation: No response body.

Before:

When getting information for key 'test.csv' in bucket 'pcmoritz-test-bucket-arrow-errors': AWS Error [code 15]: No response body.

For comparison, this is how the same information is incorporated into boto3 errors:

ClientError: An error occurred (400) when calling the HeadObject operation: Bad Request

I'm happy to use the exact same phrasing as boto3 if that's desired -- I'll do a follow up PR with the error codes substituted with actual errors and can change it then if desired.

@pcmoritz pcmoritz merged commit b43c6f6 into apache:master Aug 30, 2022
@pcmoritz pcmoritz deleted the aws-s3-error-messages branch August 30, 2022 03:47
@ursabot
Copy link

ursabot commented Aug 30, 2022

Benchmark runs are scheduled for baseline = d7eea09 and contender = b43c6f6. b43c6f6 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Failed] test-mac-arm
[Failed ⬇️0.55% ⬆️0.0%] ursa-i9-9960x
[Failed] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] b43c6f6b ec2-t3-xlarge-us-east-2
[Failed] b43c6f6b test-mac-arm
[Failed] b43c6f6b ursa-i9-9960x
[Finished] b43c6f6b ursa-thinkcentre-m75q
[Finished] d7eea09b ec2-t3-xlarge-us-east-2
[Failed] d7eea09b test-mac-arm
[Failed] d7eea09b ursa-i9-9960x
[Failed] d7eea09b ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

@ursabot
Copy link

ursabot commented Aug 30, 2022

['Python', 'R'] benchmarks have high level of regressions.
ursa-i9-9960x

anjakefala pushed a commit to anjakefala/arrow that referenced this pull request Aug 31, 2022
)

First part of improving error messages from S3 operations. We include the operation that failed in the error message now. This makes it easier to debug problems (e.g. bucket permissions or other infrastructure hickups) because it allows to re-run the operation that failed with the AWS CLI for further diagnosing what is going wrong.

Example (changes in bold):

> When getting information for key 'test.csv' in bucket 'pcmoritz-test-bucket-arrow-errors': AWS Error [code 15] **during HeadObject operation**: No response body.

Authored-by: Philipp Moritz <[email protected]>
Signed-off-by: Philipp Moritz <[email protected]>
zagto pushed a commit to zagto/arrow that referenced this pull request Oct 7, 2022
)

First part of improving error messages from S3 operations. We include the operation that failed in the error message now. This makes it easier to debug problems (e.g. bucket permissions or other infrastructure hickups) because it allows to re-run the operation that failed with the AWS CLI for further diagnosing what is going wrong.

Example (changes in bold):

> When getting information for key 'test.csv' in bucket 'pcmoritz-test-bucket-arrow-errors': AWS Error [code 15] **during HeadObject operation**: No response body.

Authored-by: Philipp Moritz <[email protected]>
Signed-off-by: Philipp Moritz <[email protected]>
fatemehp pushed a commit to fatemehp/arrow that referenced this pull request Oct 17, 2022
)

First part of improving error messages from S3 operations. We include the operation that failed in the error message now. This makes it easier to debug problems (e.g. bucket permissions or other infrastructure hickups) because it allows to re-run the operation that failed with the AWS CLI for further diagnosing what is going wrong.

Example (changes in bold):

> When getting information for key 'test.csv' in bucket 'pcmoritz-test-bucket-arrow-errors': AWS Error [code 15] **during HeadObject operation**: No response body.

Authored-by: Philipp Moritz <[email protected]>
Signed-off-by: Philipp Moritz <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants