mamdouhtawfik commented on issue #45240: URL: https://github.com/apache/airflow/issues/45240#issuecomment-2567485697
I had a deeper look into the issue and I think the issue is related to a "bug" in the xcom.py file, it was resolved in this PR https://github.com/apache/airflow/pull/37058/files#diff-3f95f161bd9ef4bb455611e0c58583899769360afc53f755cd1577cf194553c5R423, calling the XCom variable to deserialize the value instead of BaseXCom class. I am not sure if there is an easy way to address this within airflow 2.8.1 @mohamedmeqlad99 thanks for spending time to try to support with this, yet I am not sure if your PR is addressing the issue here and generally I don't think we should go in an S3 specific path but rather use the deserialization of the customer xcom backend (which is what was "fixed" in the PR I shared) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
