-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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] AirflowInstance, sensor refactor #23538
Conversation
|
||
@property | ||
def end_date(self) -> float: | ||
return AirflowInstance.timestamp_from_airflow_date(self.metadata["end_date"]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At some point we might cross the threshold of wanting to use an openapi-generated client https://github.com/apache/airflow-client-python
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All seems reasonable to me. As I noted, at some point it might make sense to either take a dependency or vendor an open-api generated client.
7ffd167
to
e9f5927
Compare
7a2a739
to
f497897
Compare
e9f5927
to
f692103
Compare
f497897
to
d6d0f56
Compare
d6d0f56
to
5a69ee2
Compare
…well-typed properties
5a69ee2
to
bc014a2
Compare
Made the AirflowInstance vended classes more composable so we're not throwing around raw dicts everywhere. Added some utilities to trigger and wait for the completion of airflow runs, which are used in tests (for now...) Made some refactors to the sensor after realizing we don't actually want to report in topological order... we want to report in task order. So instead, retrieve per-task info about each execution. Better testing of this new method is forthcoming, but existing tests already exercise the codepath.
Made the AirflowInstance vended classes more composable so we're not throwing around raw dicts everywhere. Added some utilities to trigger and wait for the completion of airflow runs, which are used in tests (for now...)
Made some refactors to the sensor after realizing we don't actually want to report in topological order... we want to report in task order. So instead, retrieve per-task info about each execution. Better testing of this new method is forthcoming, but existing tests already exercise the codepath.