chore: remove memory limits from certified GA destinations - #67078
Merged
Merged
Conversation
Remove memory_limit from sync job resourceRequirements for 4 certified GA destinations: - destination-s3 (1.9.2 → 1.9.3) - destination-bigquery (3.0.7 → 3.0.8) - destination-azure-blob-storage (1.1.1 → 1.1.2) - destination-redshift (3.5.3 → 3.5.4) This change improves performance and resource utilization by removing artificial memory caps while keeping memory_request intact. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Davin Chia (davinchia)
marked this pull request as ready for review
October 6, 2025 05:04
Contributor
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. Helpful Resources
PR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
|
- Add changelog entries to docs for version updates - Remove standalone CHANGELOG.md files in connector directories - Changelogs are maintained in the documentation files per project convention 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Replace TBD with actual PR number 67078 in all documentation changelogs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
|
Contributor
|
Contributor
|
Contributor
|
Reverting destination-redshift changes due to test failures. Will be handled separately. - Restore version to 3.5.3 - Restore memory_limit in metadata.yaml - Remove changelog entry from docs 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Francis Genet (frifriSF59)
approved these changes
Oct 6, 2025
Benoit Moriceau (benmoriceau)
approved these changes
Oct 6, 2025
Contributor
|
Deploy preview for airbyte-docs ready! ✅ Preview Built with commit 3aec2e3. |
Contributor
Author
|
Even though the build is red, all the other builds have passed at least one in separate runs, so I'm merging this in. |
Matteo Palarchio (matteogp)
pushed a commit
that referenced
this pull request
Oct 10, 2025
Remove memory_limit from sync job resourceRequirements for 4 certified GA destinations: destination-s3 (1.9.2 → 1.9.3) destination-bigquery (3.0.7 → 3.0.8) destination-azure-blob-storage (1.1.1 → 1.1.2) This change improves performance and resource utilization by removing artificial memory caps while keeping memory_request intact. Limits are mostly a cost concern, and connector devs shouldn't need to set them to begin with. 🤖 Generated with Claude Code Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Remove memory_limit from sync job resourceRequirements for 4 certified GA destinations:
This change improves performance and resource utilization by removing artificial memory caps while keeping memory_request intact.
Limits are mostly a cost concern, and connector devs shouldn't need to set them to begin with.
🤖 Generated with Claude Code
How
Remove.
Excluding Redshift as those tests are failing.
Excluding Snowflake since it's actively being worked on. The change will happen in the next breaking change.
Review guide
User Impact
Can this PR be safely reverted and rolled back?