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 alert & retry for delta/s3 initialization #74

Merged
merged 2 commits into from
Aug 1, 2024
Merged

Conversation

oguzhanunlu
Copy link
Contributor

@oguzhanunlu oguzhanunlu commented Jul 31, 2024

ref: PDP-1322

@oguzhanunlu oguzhanunlu self-assigned this Jul 31, 2024
@oguzhanunlu oguzhanunlu marked this pull request as draft July 31, 2024 11:34
Comment on lines 46 to 49
case _: AccessDeniedException =>
// 1 - no permission to see s3 bucket
// 2 - not authorized to assume the role
true
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please can you explain to me under which circumstances you get a AccessDeniedException?

Can you confirm I've understood your code comments correctly....

  • If the bucket doesn't exist, or we don't have permission to see the bucket itself --> get a UnknownStoreException
  • If we don't have access to read/write objects inside the bucket --> get a DeltaIOException

...so I can't work out what scenario gives a AccessDeniedException.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I can't work out what scenario gives a AccessDeniedException.

we get AccessDeniedException in these cases:

  • when the bucket's policy denies all actions, we get AccessDeniedException without any error message
  • when we try to assume a role that doesn't exist, we get AccessDeniedException with detailed error message

I see that my comment on L47 is misleading

Copy link
Contributor Author

Choose a reason for hiding this comment

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

just pushed a commit to describe exact situation

@oguzhanunlu oguzhanunlu marked this pull request as ready for review August 1, 2024 14:25
@oguzhanunlu oguzhanunlu merged commit c2c088a into develop Aug 1, 2024
2 checks passed
@oguzhanunlu oguzhanunlu deleted the delta-init branch August 1, 2024 14:33
zhaow-de added a commit to alloy-ch/rcplus-alloy-snowplow-lake-loader that referenced this pull request Oct 4, 2024
…patch-for-alloy

* commit '7ab2edc3fd4d81ffb4d5f3285d02330def7672b1':
  Upgrade common-streams to 0.8.0-M5
  Delete files asynchronously (snowplow-incubator#82)
  Upgrade common-streams 0.8.0-M4 (snowplow-incubator#81)
  Avoid error on duplicate view name (snowplow-incubator#80)
  Add option to exit on missing Iglu schemas (snowplow-incubator#79)
  common-streams 0.8.x with refactored health monitoring (snowplow-incubator#78)
  Create table concurrently with subscribing to stream of events (snowplow-incubator#77)
  Iceberg fail fast if missing permissions on the catalog (snowplow-incubator#76)
  Make alert messages more human-readable (snowplow-incubator#75)
  Hudi loader should fail early if missing permissions on Glue catalog (snowplow-incubator#72)
  Add alert & retry for delta/s3 initialization (snowplow-incubator#74)
  Implement alerting and retrying mechanisms
  Bump aws-hudi to 1.0.0-beta2 (snowplow-incubator#71)
  Bump hudi to 0.15.0 (snowplow-incubator#70)
  Allow disregarding Iglu field's nullability when creating output columns (snowplow-incubator#66)
  Extend health probe to report unhealthy on more error scenarios (snowplow-incubator#69)
  Fix bad rows resizing (snowplow-incubator#68)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants