Mohammed-Karim226 opened a new issue, #46016:
URL: https://github.com/apache/airflow/issues/46016

   ### Apache Airflow version
   
   main (development)
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   In PR #38264, a few Task properties in the AirflowRunFacet were accidentally 
removed. This caused missing serialization of these properties, which are 
necessary for proper functionality in the OpenLineage provider.
   
   
   ### What you think should happen instead?
   
   The removed Task properties should be serialized in the AirflowRunFacet as 
they were before PR #38264. This ensures compatibility and correct 
functionality for OpenLineage integration.
   
   
   ### How to reproduce
   
   Use an Airflow deployment with OpenLineage provider enabled.
   
   Check the serialized output of AirflowRunFacet for Task properties.
   
   Observe that certain properties are missing after PR #38264.
   
   ### Operating System
   
   N/A (This is a code-level issue, not OS-specific.)
   
   ### Versions of Apache Airflow Providers
   
   
[providers-ydb/1.0.0rc1](https://github.com/apache/airflow/releases/tag/providers-ydb%2F1.0.0rc1)
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   N/A  (This is a code-level issue, not deployment-specific.)
   
   ### Anything else?
   
   ### Frequency
   This issue occurs consistently for any Task using the affected 
AirflowRunFacet properties.
   
   ### Fix
   The issue was resolved in PR #40371, which reintroduced the missing 
properties.
   
   ### 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]

Reply via email to