mamdouhtawfik opened a new issue, #45240: URL: https://github.com/apache/airflow/issues/45240
### Apache Airflow Provider(s) databricks ### Versions of Apache Airflow Providers 6.0.0 ### Apache Airflow version 2.8.1 ### Operating System Amazon ### Deployment Amazon (AWS) MWAA ### Deployment details _No response_ ### What happened When I click on the link to see job run details, it directs to https://(s3 path of my xcom json file), instead of directing to databricks workspace ### What you think should happen instead I expect the link to work and directs to job run details in our team's databricks workspace ### How to reproduce 1. Create and use a custom XCOM backend that writes to S3 2. Run a databricks job 3. Click the link to go to the job run details 4. Airflow 404 ### Anything else Currently our custom XCOM backend, stores everything in S3, it does not store large values only as other XCOM, yet the behavior of the extra link should not depend on that: I had a look at https://airflow.apache.org/docs/apache-airflow-providers-databricks/6.0.0/_modules/airflow/providers/databricks/operators/databricks.html#DatabricksJobRunLink.get_link and https://github.com/apache/airflow/blob/2.8.1/airflow/models/xcom.py#L873-L876 yet I doubt that TYPE_CHECKING is true during runtime, because if it is, then the provider won't use our custom class. I also tried to override the orm_deserialize_value method hoping this will fix the issue, yet I ran into the issue I mentioned in this comment https://github.com/apache/airflow/discussions/44232#discussioncomment-11636619 (contributions to this discussion are very welcome as well) ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
