roykoand commented on PR #60001: URL: https://github.com/apache/airflow/pull/60001#issuecomment-3707113868
> What's the use case for this? BaseXcom is needed for writing custom backends only Hi @amoghrajesh, Thanks for looking into this! I have a fairly standard use case of storing XComs in object storage with some custom modifications. The current implementation predates `airflow.providers.common.io.xcom.backend.XComObjectStorageBackend`, which is why it wasn't used initially. While I could likely refactor it to use `XComObjectStorageBackend`, I thought including `BaseXCom` in `common.compat` would be beneficial (and easier for me...). At a minimum, it would allow us to simplify at least one occurrence 😆 https://github.com/apache/airflow/blob/4745dc53d9d38094acc7119a634aed9ed243f9da/providers/common/io/src/airflow/providers/common/io/xcom/backend.py#L37-L42 -- 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]
