-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Dataset, Model asset subclasses #43142
Conversation
01b332d
to
044ee6b
Compare
218c7fe
to
b300945
Compare
Talked to Constance earlier; we should probably still make Same for DatasetAlias; this one is not as important (I doubt many people are already using it aside from Cosmos), but we might as well add it since the mechanism is the same. Those names should be removed in Airflow 3.2. |
Sounds good. Will do |
beb4d3a
to
ceefc1c
Compare
Updated |
…"airflow.datasets.DatasetAlias" import for backward compat
ceefc1c
to
1e2f92e
Compare
* feat(assets): add dataset subclass * feat(assets): add model subclass * feat(assets): make group a default instead of overwriting user input * feat(assets): allow "airflow.Dataset" and "airflow.datasets.Dataset", "airflow.datasets.DatasetAlias" import for backward compat
* feat(assets): add dataset subclass * feat(assets): add model subclass * feat(assets): make group a default instead of overwriting user input * feat(assets): allow "airflow.Dataset" and "airflow.datasets.Dataset", "airflow.datasets.DatasetAlias" import for backward compat
* feat(assets): add dataset subclass * feat(assets): add model subclass * feat(assets): make group a default instead of overwriting user input * feat(assets): allow "airflow.Dataset" and "airflow.datasets.Dataset", "airflow.datasets.DatasetAlias" import for backward compat
Close: #42312
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.