Repository navigation
S3 destinations: use STANDARD retry mode - #24736
Conversation
Affected Connector ReportNOTE
|
| Connector | Version | Changelog | Publish |
|---|
- See "Actionable Items" below for how to resolve warnings and errors.
✅ Destinations (10)
| Connector | Version | Changelog | Publish |
|---|---|---|---|
destination-bigquery |
1.2.19 |
✅ | ✅ |
destination-bigquery-denormalized |
1.2.19 |
✅ | ✅ |
destination-databricks |
1.0.0 |
✅ | ✅ |
destination-gcs |
0.2.16 |
✅ | ✅ |
destination-jdbc |
0.3.14 |
🔵 (ignored) |
🔵 (ignored) |
destination-r2 |
0.1.0 |
✅ | ✅ |
destination-redshift |
0.4.5 |
✅ | ✅ |
destination-s3 |
0.3.23 |
✅ | ✅ |
destination-s3-glue |
0.1.4 |
✅ | ✅ |
destination-snowflake |
0.4.61 |
✅ | ✅ |
- See "Actionable Items" below for how to resolve warnings and errors.
👀 Other Modules (1)
- base-normalization
Actionable Items
(click to expand)
| Category | Status | Actionable Item |
|---|---|---|
| Version | ❌ mismatch |
The version of the connector is different from its normal variant. Please bump the version of the connector. |
| ⚠ doc not found |
The connector does not seem to have a documentation file. This can be normal (e.g. basic connector like source-jdbc is not published or documented). Please double-check to make sure that it is not a bug. |
|
| Changelog | ⚠ doc not found |
The connector does not seem to have a documentation file. This can be normal (e.g. basic connector like source-jdbc is not published or documented). Please double-check to make sure that it is not a bug. |
| ❌ changelog missing |
There is no chnagelog for the current version of the connector. If you are the author of the current version, please add a changelog. | |
| Publish | ⚠ not in seed |
The connector is not in the seed file (e.g. source_definitions.yaml), so its publication status cannot be checked. This can be normal (e.g. some connectors are cloud-specific, and only listed in the cloud seed file). Please double-check to make sure that it is not a bug. |
| ❌ diff seed version |
The connector exists in the seed file, but the latest version is not listed there. This usually means that the latest version is not published. Please use the /publish command to publish the latest version. |
|
/test connector=connectors/destination-s3
Build PassedTest summary info: |
|
/publish connector=connectors/destination-s3
if you have connectors that successfully published but failed definition generation, follow step 4 here |
|
/publish connector=connectors/destination-snowflake
if you have connectors that successfully published but failed definition generation, follow step 4 here |
|
/publish connector=connectors/destination-redshift
if you have connectors that successfully published but failed definition generation, follow step 4 here |
|
/test connector=connectors/destination-snowflake |
What
Try to improve how we respond to s3 rate-limiting errors (https://github.com/airbytehq/oncall/issues/1758#issuecomment-1490412590)
How
As title. According to the docs (https://docs.aws.amazon.com/sdkref/latest/guide/feature-retry-behavior.html), we were previously defaulting to LEGACY mode. The aws-java-sdk-core javadoc has this description for STANDARD:
which sounds like better handling for a 503
SlowDownresponse?I have no idea how to actually test this though.