Remove old lineage stuff

[uranusjr]

Body

We had some experiemental lineage classes in airflow.lineage. Those never caught on, and are not relevant anymore now that we have assets and trasparent OpenLineage support via AIP-62. We should remove the old stuff in 3.0, and put up a deprecation warning in 2.11 if not already.

Committer

• I acknowledge that I am a maintainer/committer of the Apache Airflow project.

[jason810496]

Hi @uranusjr, I can work on this issue, could you assign to me ? Thanks !

[ashb]

@jason810496 All yours!

[jason810496]

Hi, I have a few questions while working on this issue:

• The compatibility module (airflow.providers.common.compat.lineage) still imports the airflow.lineage module. Does this mean I should move airflow.lineage to airflow.providers.common.compat.lineage instead of simply deleting it?
• For other airflow modules that import airflow.lineage, can all logic involving lineage be removed?

Thanks !

[Lee-W]

* The compatibility module (`airflow.providers.common.compat.lineage`) still imports the `airflow.lineage` module. Does this mean I should move `airflow.lineage` to `airflow.providers.common.compat.lineage` instead of simply deleting it?

I think so. As not every users upgrade to 3.0 right after release.

* For other `airflow` modules that import `airflow.lineage`, can all logic involving `lineage` be removed?

We probably need to list what are other airflow modules that import airflow.lineage`. But if if the issue is already created here, I guess it's safe to remove them 🤔