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

[dagster-airlift] 0.0.27 #25378

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions examples/experimental/dagster-airlift/CHANGES.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,35 @@
# Changelog

## 0.0.27

### New

- Airlift CLI: You can now proxy airlift state in your airflow directory by calling `dagster-airlift proxy scaffold` from within your Airflow codebase (airflow must be installed, and `AIRFLOW_HOME` must be set)
- `dagster-airlift[in-airflow]` no longer has a direct pin on airflow itself. Instead we rely on users installing their own 2.0.0 or greater version of Airflow.
- Dag-level mapping has been introduced. Using the `assets_with_dag_mappings` API, you can map individual assets to an entire DAG, and those assets will receive materializations on successful runs of that DAG. See the tutorial section on dag-level mapping for more.
- Python 3.12 is now explicitly supported.
- Time-windowed partitioned assets mapped to Airflow will now automatically receive partitioned materializations corresponding to the `execution_date` in airflow. See the tutorial section on partitioning for more.

### Tutorial

- Tutorial section on dealing with changing airflow
- Tutorial section on partitioning
- Tutorial section on dag-level mapping
- The tutorial has been changed to use `assets_with_task_mappings` instead of `task_defs` to maintain a consistent API across integrations.

### Breaking Changes

- Proxy operators now makes the assumption that all assets mapped to a given airflow task must be launchable within a single run (this works out of the box on Dagster 1.8 or greater).
- The `dagster_operator_klass` method has been removed, and the base class has changed. Instead of overriding `BaseProxyToDagsterOperator`, users will now subclass `BaseProxyTaskToDagsterOperator`, and use the `build_from_task_fn` argument:

```python
proxying_to_dagster(
...,
# This method is implemented by default, but can be overridden.
build_from_task_fn=MyCustomOperator.build_from_task,
)
```

## 0.0.26

### New
Expand Down
2 changes: 1 addition & 1 deletion examples/experimental/dagster-airlift/setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ def get_version() -> str:

setup(
name="dagster-airlift",
version="0.0.26",
version="0.0.27",
author="Dagster Labs",
author_email="[email protected]",
license="Apache-2.0",
Expand Down