GitHub user jgoedeke added a comment to the discussion: Airflow s3 xcom backend - Show the xcom values in airflow UI than the s3 path for the xcom
We have the same need with `XComObjectStorageBackend`: viewing the actual JSON content in the UI, including when the stored object is gzip-compressed. Could an explicit “Preview stored XCom” action be considered? Rather than automatically loading remote values, it could: - Fetch content only when the user clicks Preview. - Respect the existing DAG/XCom read permissions. - Show JSON/text without reconstructing Python objects. - Enforce a decompressed-size limit and timeout. - Leave the current reference-only display unchanged for normal browsing. - Keep storage access and decompression provider-specific. Another possibility for S3-compatible storage is generating a short-lived presigned URL with `Content-Encoding: gzip` and `Content-Type: application/json`. The browser could then decompress the existing object without creating an uncompressed copy, provided the storage supports those response-header overrides and is reachable from the browser. Would either approach fit Airflow 3’s architecture? GitHub link: https://github.com/apache/airflow/discussions/44232#discussioncomment-19072665 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
