-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
feat: implement amazon s3 to dynamodb transfer operator #39654
Merged
vincbeck
merged 1 commit into
apache:main
from
dondaum:feat/airflow-providers-amazon-add-s3todynamidboperator
May 27, 2024
Merged
feat: implement amazon s3 to dynamodb transfer operator #39654
vincbeck
merged 1 commit into
apache:main
from
dondaum:feat/airflow-providers-amazon-add-s3todynamidboperator
May 27, 2024
Conversation
This file contains 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
boring-cyborg
bot
added
area:providers
area:system-tests
kind:documentation
provider:amazon-aws
AWS/Amazon - related issues
labels
May 15, 2024
dondaum
force-pushed
the
feat/airflow-providers-amazon-add-s3todynamidboperator
branch
from
May 15, 2024 22:07
513a641
to
6d4e399
Compare
vincbeck
reviewed
May 16, 2024
dondaum
force-pushed
the
feat/airflow-providers-amazon-add-s3todynamidboperator
branch
from
May 16, 2024 21:28
6d4e399
to
22c96e2
Compare
vincbeck
reviewed
May 16, 2024
dondaum
force-pushed
the
feat/airflow-providers-amazon-add-s3todynamidboperator
branch
2 times, most recently
from
May 17, 2024 09:02
69992d1
to
b2cb654
Compare
vincbeck
reviewed
May 17, 2024
vincbeck
reviewed
May 17, 2024
dondaum
force-pushed
the
feat/airflow-providers-amazon-add-s3todynamidboperator
branch
from
May 17, 2024 19:16
b2cb654
to
36bdf06
Compare
vincbeck
reviewed
May 17, 2024
dondaum
force-pushed
the
feat/airflow-providers-amazon-add-s3todynamidboperator
branch
2 times, most recently
from
May 17, 2024 19:54
1b84fd8
to
b67c059
Compare
raphaelauv
reviewed
May 20, 2024
dondaum
force-pushed
the
feat/airflow-providers-amazon-add-s3todynamidboperator
branch
from
May 20, 2024 20:46
b67c059
to
3f66216
Compare
dondaum
force-pushed
the
feat/airflow-providers-amazon-add-s3todynamidboperator
branch
from
May 21, 2024 10:20
3f66216
to
3016cf2
Compare
Retriggered CI. |
vincbeck
approved these changes
May 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
closes: #39377
Implements a new transfer operator for loading Amazon S3 data into an Amazon DynamoDB table. The operator uses the existing
ImportTable
AWS Service. Yet, import into existing tables is not currently supported byImportTable
. Until this is supported the operator uses an combination of staging first into a temporary DynamoDB table and then usescan
to load data into the target DynamoDB table.All related unit tests, CI, and build-docs inlcuding system test pass locally.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.