Uh oh!
There was an error while loading. Please reload this page.
AIP-84: Migrating GET queued asset events for DAG to fastAPI - #43934
Conversation
3af2873 to
2cd5dc1Compare@pierrejeambrun FYI, I have pushed the changes for all the "resolved" comments. The rest are open for input from you. EDIT: I kept the endpoint at public/dags.py cos if I move to assets, the path will become: |
Uh oh!
There was an error while loading. Please reload this page.
pierrejeambrun
left a comment
There was a problem hiding this comment.
Small suggestions / questions almost ready
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
pierrejeambrun
left a comment
There was a problem hiding this comment.
As many of other PRs depends on this one, to try to make them move forward I added a few commits, I think it's ready
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
…43934) * AIP-84: Migrating GET queued asset events for DAG to fastAPI * adding test cases * adding setup and teardown * review comments part 1 * introducing _generate_queued_event_where_clause * changing to bad request * adding paginated_select * moving _generate_queued_event_where_clause to assets.py * moving datamodels to assets * moving tests to assets * reuse fixtures from TestGetAssets and inherit classes to simplify * Move route to assets module * Small adjustments --------- Co-authored-by: pierrejeambrun <pierrejbrun@gmail.com>
related: #42370
Migrating the GET queued asset events for a DAG endpoint to fast API.
Setup:
Created producer and consumer dags:

Paused one producer while running the other to generate queued events

Responses:
Legacy

FastAPI

With time filtering:
(Beyond creation time)

(Beyond creation time)

Swagger spec: (maintained under dag section)

^ 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.rstor{issue_number}.significant.rst, in newsfragments.