Skip to content
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

Move Asset user facing components to task_sdk #43773

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

Lee-W
Copy link
Member

@Lee-W Lee-W commented Nov 7, 2024

Why

As part of AIP-72

Closes: #43619

What

  • Move "Asset", "AssetAll", "AssetAny", "Dataset", "Model" from Airflow Core to task_sdk
  • Import Asset from task_sdk for common.compat provider
  • Fix ImportError handling in common.compat provider
    • Add a temporary workaround for this error for the following providers (which should be removed after common.compat provider change in this PR has been released)
      • providers/openlineage
      • providers/google
      • providers/amazon

^ 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.

@Lee-W Lee-W added the legacy api Whether legacy API changes should be allowed in PR label Nov 7, 2024
@Lee-W Lee-W force-pushed the move-asset-to-task-sdk branch 6 times, most recently from c7ecee5 to 5c8d6e2 Compare November 7, 2024 10:02
@Lee-W Lee-W marked this pull request as ready for review November 7, 2024 11:40
@Lee-W Lee-W changed the title Move asset to task_sdk Move Asset user facing components to task_sdk Nov 7, 2024
@Lee-W Lee-W added airflow3.0:breaking Candidates for Airflow 3.0 that contain breaking changes AIP-72 Task Execution Interface aka Task SDK labels Nov 7, 2024
@Lee-W Lee-W force-pushed the move-asset-to-task-sdk branch 3 times, most recently from 4bba78f to 17079b8 Compare November 8, 2024 06:00
@@ -85,15 +85,15 @@
"version": (".version", "", False),
# Deprecated lazy imports
"AirflowException": (".exceptions", "AirflowException", True),
"Dataset": (".assets", "Dataset", True),
"Dataset": (".sdk.definitions.asset", "Dataset", True),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also change the line for Asset right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should keep it as Dataset. I think we're using the subclass Dataset(Asset) here

@Lee-W Lee-W force-pushed the move-asset-to-task-sdk branch 7 times, most recently from befbbbf to 97d78b2 Compare November 8, 2024 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AIP-72 Task Execution Interface aka Task SDK airflow3.0:breaking Candidates for Airflow 3.0 that contain breaking changes area:API Airflow's REST/HTTP API area:lineage area:providers area:Scheduler including HA (high availability) scheduler area:serialization area:webserver Webserver related Issues kind:documentation legacy api Whether legacy API changes should be allowed in PR provider:common-compat
Development

Successfully merging this pull request may close these issues.

Move Asset user-facing components to task_sdk
2 participants