-
Notifications
You must be signed in to change notification settings - Fork 15.4k
Use BaseXCom serialize_value when objectstorage_threshold is less than given input #49173
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
Use BaseXCom serialize_value when objectstorage_threshold is less than given input #49173
Conversation
providers/common/io/src/airflow/providers/common/io/xcom/backend.py
Outdated
Show resolved
Hide resolved
Post update: @vatsrahul1001 ![]() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, one comment
# likely, we need to deserialize it using json.loads | ||
data = json.loads(base_xcom_deser_result, cls=XComDecoder) | ||
except (TypeError, ValueError): | ||
pass |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we re raise this one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine, this raises error happen only when base_xcom_deser_result is object store path, likely this is string that means we should continue to next below to read from ObjectStore with path. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep seems ok
closes: #49159
^ 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 airflow-core/newsfragments.