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

Improve flint error handling #335

Merged
merged 3 commits into from
May 11, 2024

Conversation

noCharger
Copy link
Collaborator

@noCharger noCharger commented May 9, 2024

Description

Improve flint error handling

  • Add jobType in result metadata
  • Refactor error field format of result metadata
    • Redact sensitive info for Glue AccessDeniedException in error message
    • Add service name in error field of result metadata
    • Add status code in error field of result metadata
  • Remove unused params in handleQueryException

Issues Resolved

List any issues this PR will resolve, e.g. Closes [...].

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@noCharger noCharger force-pushed the improve-err branch 3 times, most recently from ae48ce8 to e24c398 Compare May 10, 2024 06:33
@noCharger noCharger marked this pull request as ready for review May 10, 2024 06:39
@noCharger noCharger force-pushed the improve-err branch 2 times, most recently from c54be0c to bd1fc2e Compare May 10, 2024 18:32
@noCharger noCharger added 0.3 backport 0.3 enhancement New feature or request labels May 10, 2024
@noCharger noCharger self-assigned this May 10, 2024
Signed-off-by: Louis Chu <clingzhi@amazon.com>
Signed-off-by: Louis Chu <clingzhi@amazon.com>
Signed-off-by: Louis Chu <clingzhi@amazon.com>
@noCharger noCharger merged commit 45835cb into opensearch-project:main May 11, 2024
4 checks passed
@opensearch-trigger-bot
Copy link

The backport to 0.3 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/opensearch-spark/backport-0.3 0.3
# Navigate to the new working tree
pushd ../.worktrees/opensearch-spark/backport-0.3
# Create a new branch
git switch --create backport/backport-335-to-0.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 45835cb27407166669f660cc665436ed6cc93200
# Push it to GitHub
git push --set-upstream origin backport/backport-335-to-0.3
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/opensearch-spark/backport-0.3

Then, create a pull request where the base branch is 0.3 and the compare/head branch is backport/backport-335-to-0.3.

noCharger added a commit that referenced this pull request May 11, 2024
* Improve flint error handling

Signed-off-by: Louis Chu <clingzhi@amazon.com>

* Error field in json format

Signed-off-by: Louis Chu <clingzhi@amazon.com>

* Superset update

Signed-off-by: Louis Chu <clingzhi@amazon.com>

---------

Signed-off-by: Louis Chu <clingzhi@amazon.com>
(cherry picked from commit 45835cb)
noCharger added a commit that referenced this pull request May 11, 2024
* Improve flint error handling

Signed-off-by: Louis Chu <clingzhi@amazon.com>

* Error field in json format

Signed-off-by: Louis Chu <clingzhi@amazon.com>

* Superset update

Signed-off-by: Louis Chu <clingzhi@amazon.com>

---------

Signed-off-by: Louis Chu <clingzhi@amazon.com>
(cherry picked from commit 45835cb)
noCharger added a commit that referenced this pull request May 11, 2024
case r: AnalysisException =>
Some(r.getServiceName),
Some(r.getStatusCode))
case r: AWSGlueException =>

Choose a reason for hiding this comment

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

Can we also add handling for permission errors to S3, OpenSearch as well?

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