amoghrajesh commented on issue #49456: URL: https://github.com/apache/airflow/issues/49456#issuecomment-2955073842
Thanks @kaxil! I agree with most of your assessment, but I have a qn / disagree with one point. > Now, because we are sure that the value stored in DB will always be a valid JSON object, it is safe to de-serialize it using our Serializer. We don't need to use Custom XCom backend to display in the UI at least. For cases when a user deploys a custom xcom backend, lets say such as: https://github.com/apache/airflow/blob/main/airflow-core/tests/unit/api_fastapi/core_api/routes/public/test_xcom.py#L93-L94 When the user uses an API and calls in with `deserialize` set to true OR if we make the change so that UI can send "deserialize" True. It will still not return response that has been deserialized with the user configured deserializer. Would that not create a discrepancy in the way users expect a response? -- 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]
