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

[Feature]Open source AirflowFlyteOperator (@Lyft) for better integration with airflow #544

Closed
1 of 13 tasks
kumare3 opened this issue Oct 8, 2020 · 1 comment
Closed
1 of 13 tasks
Assignees
Labels
enhancement New feature or request flytekit FlyteKit Python related issue plugins Plugins related labels (backend or frontend)

Comments

@kumare3
Copy link
Contributor

kumare3 commented Oct 8, 2020

Motivation: Why do you think this is important?
As many of the OSS users are on Airflow, it would really help the community to have AirflowFlyteOperator available in Open Source. This would make it possible to use Flyte when some existing workflows are leveraging Airflow.

Goal: What should the final outcome look like, ideally?
Users using Airflow should be able to leverage Flyte when possible and it should be possible to add a new step in the Airflow DAG, which runs the execution on Flyte

Describe alternatives you've considered
This is possible to do by install flytekit and writing an operator themselves or using the PythonOperator, but this has a higher learning curve and needs more work on the user.

Flyte component

  • Overall
  • Flyte Setup and Installation scripts
  • Flyte Documentation
  • Flyte communication (slack/email etc)
  • FlytePropeller
  • FlyteIDL (Flyte specification language)
  • Flytekit (Python SDK)
  • FlyteAdmin (Control Plane service)
  • FlytePlugins
  • DataCatalog
  • FlyteStdlib (common libraries)
  • FlyteConsole (UI)
  • Other

[Optional] Propose: Link/Inline
Operator interface:
(Project: str, Domain:str , LaunchPlanName:str, version: str=None, flyte_kwargs: Dict[str, Any]=None)

Steps

  1. Retrieve Launch Plan using ("project", "domain", "name", [optional: "version"]). If version is not specified retrieve latest
  2. Execute the launch plan with inputs=flyte_kwargs and generate a deterministic name for the run with the attempt number
  3. Wait for the execution to complete
  4. OnKill, pass the kill switch to Flyte

Is this a blocker for you to adopt Flyte
NA

@kumare3 kumare3 added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels Oct 8, 2020
@kumare3 kumare3 added this to the 0.10.0 milestone Oct 8, 2020
@EngHabu EngHabu removed this from the 0.10.0 milestone Jan 11, 2021
@kumare3 kumare3 added flytekit FlyteKit Python related issue and removed untriaged This issues has not yet been looked at by the Maintainers labels Jan 14, 2022
@cosmicBboy cosmicBboy added the plugins Plugins related labels (backend or frontend) label Apr 21, 2022
@samhita-alla
Copy link
Contributor

eapolinario pushed a commit to eapolinario/flyte that referenced this issue Jul 24, 2023
* Remove resource injection on the node for container task

Signed-off-by: byhsu <[email protected]>

* fix conflict

Signed-off-by: byhsu <[email protected]>

* fix lint

Signed-off-by: byhsu <[email protected]>

* downgrade plugin

Signed-off-by: byhsu <[email protected]>

---------

Signed-off-by: byhsu <[email protected]>
Co-authored-by: byhsu <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 9, 2023
* Remove resource injection on the node for container task

Signed-off-by: byhsu <[email protected]>

* fix conflict

Signed-off-by: byhsu <[email protected]>

* fix lint

Signed-off-by: byhsu <[email protected]>

* downgrade plugin

Signed-off-by: byhsu <[email protected]>

---------

Signed-off-by: byhsu <[email protected]>
Co-authored-by: byhsu <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request flytekit FlyteKit Python related issue plugins Plugins related labels (backend or frontend)
Projects
None yet
Development

No branches or pull requests

4 participants