We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
You can continue the conversation there. Go to discussion →
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
If a large amount of s3 data is moved using s3 to gcs, data too long for column error occurs when storing related values in the last xcom
I think we can prevent this error by adding a logic that compresses the list to show only some of the data
No response
The text was updated successfully, but these errors were encountered:
XCOM is not for data , it's for metadata ( xcom backend is just a work around , in all case Airlfow should not see your data )
Airflow is a scheduling tool not an ETL tool
Airlfow operators are most of them simple python helpers not data-transfert efficient tools
Sorry, something went wrong.
No branches or pull requests
Description
If a large amount of s3 data is moved using s3 to gcs, data too long for column error occurs when storing related values in the last xcom
Use case/motivation
I think we can prevent this error by adding a logic that compresses the list to show only some of the data
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: