[AIRFLOW-5912] Expose lineage API#7138
Conversation
|
Can you also update the documentation? |
0fbbcc5 to
1610632
Compare
Mmm yes I will. I do think this should be autogenerated in the future from a swagger definition. |
|
@bolkedebruin This month, I will start a new AIP on modernizing and hardening the API to make it fit for production use. Automatically generated documentation is one of the elements |
1610632 to
b734869
Compare
43b5c23 to
4ebf669
Compare
1f094ec to
a55ee87
Compare
|
Will do this weeknd. Seems tha the travis errors are not completely gone - we have just one thing left (CoreDNS configuration in Kind) to fix in order to be ready to move to Github Actions. |
Codecov Report
@@ Coverage Diff @@
## master #7138 +/- ##
=========================================
+ Coverage 85.24% 85.4% +0.15%
=========================================
Files 683 755 +72
Lines 39155 39758 +603
=========================================
+ Hits 33378 33954 +576
- Misses 5777 5804 +27
Continue to review full report at Codecov.
|
potiuk
left a comment
There was a problem hiding this comment.
Just some minor nits. I think for now we should let it be added in the same way as other experimental APIs until we decide what's next for the API.
Lineage data is exposed via the experimental api endpoint per dag.
dac7b33 to
f606a3a
Compare
Lineage data is exposed via the experimental api endpoint per dag.
Only lineage items obtained from XCom were rendered rather than
all. Additionally source tasks are recorded.
Issue link: AIRFLOW-5912
[AIRFLOW-NNNN]. AIRFLOW-NNNN = JIRA ID** For document-only changes commit message can start with
[AIRFLOW-XXXX].In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.