thinkORo opened a new issue, #43776:
URL: https://github.com/apache/airflow/issues/43776

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### If "Other Airflow 2 version" selected, which one?
   
   2.9.3
   
   ### What happened?
   
   I use Marquez to visualize dependencies. In Airflow I have installed 
apache-airflow-providers-openlineage and configured the OpenLineage transport:
   
   ```
   AIRFLOW__OPENLINEAGE__TRANSPORT: '{“type”: “http”, “url”: 
“http://YOUR_IP:5000”, “endpoint”: “api/v1/lineage”}'
   AIRFLOW__OPENLINEAGE__NAMESPACE: 'airflow'
   AIRFLOW__OPENLINEAGE__INCLUDE_FULL_TASK_INFO: 'true'
   ```
   
   Events and jobs are also transferred, but without the corresponding lineage. 
This means that I only see the tasks in Marquez, but not the DAG with the tasks.
   
   
   ### What you think should happen instead?
   
   In Marquez the DAG shoud be shown incl. all tasks.
   
   ### How to reproduce
   
   1. pip-install the required package: apache-airflow-providers-openlineage
   2. configure openlinage transport like so: AIRFLOW__OPENLINEAGE__TRANSPORT: 
'{“type”: “http”, “url”: “http://YOUR_IP:5000”, “endpoint”: “api/v1/lineage”}'
   3. execute any Airflow DAG
   
   ### Operating System
   
   Linux
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-openlineage==1.13.0
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### 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