Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

data to long when using s3 to gcs #39708

Closed
2 tasks done
Lee2532 opened this issue May 20, 2024 · 1 comment
Closed
2 tasks done

data to long when using s3 to gcs #39708

Lee2532 opened this issue May 20, 2024 · 1 comment
Labels
kind:feature Feature Requests needs-triage label for new issues that we didn't triage yet

Comments

@Lee2532
Copy link

Lee2532 commented May 20, 2024

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?

  • Yes I am willing to submit a PR!

Code of Conduct

@Lee2532 Lee2532 added kind:feature Feature Requests needs-triage label for new issues that we didn't triage yet labels May 20, 2024
@raphaelauv
Copy link
Contributor

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

@apache apache locked and limited conversation to collaborators May 20, 2024
@eladkal eladkal converted this issue into discussion #39715 May 20, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
kind:feature Feature Requests needs-triage label for new issues that we didn't triage yet
Projects
None yet
Development

No branches or pull requests

2 participants