Skip to content

Conversation

@gabrielgeorgiev1
Copy link
Contributor

This change lays out the initial structure for the VDK asynchronous
operator, a.k.a. the VDKSensor. The purpose of this sensor is to
routinely poke the VDK control-service and check the status of a
particular job, so that its completion/failure can trigger some
activity in an Airflow DAG, i.e. trigger another job.

Signed-off-by: Gabriel Georgiev [email protected]

This change lays out the initial structure for the VDK asynchronous
operator, a.k.a. the VDKSensor. The purpose of this sensor is to
routinely poke the VDK control-service and check the status of a
particular job, so that its completion/failure can trigger some
activity in an Airflow DAG, i.e. trigger another job.

Signed-off-by: Gabriel Georgiev <[email protected]>
Signed-off-by: Gabriel Georgiev <[email protected]>
Copy link
Contributor

@doks5 doks5 left a comment

Choose a reason for hiding this comment

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

Maybe add some docstrings about what the sensor is supposed to do. No need to be detailed (as it would be improved during the implementation process), just some high-level information.

@gabrielgeorgiev1 gabrielgeorgiev1 enabled auto-merge (squash) April 14, 2022 12:33
@gabrielgeorgiev1 gabrielgeorgiev1 merged commit 4279750 into main Apr 14, 2022
@gabrielgeorgiev1 gabrielgeorgiev1 deleted the person/gageorgiev/airflow-sensor branch April 14, 2022 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants