The Wayback Machine - https://web.archive.org/web/20210815225557/https://github.com/topics/airflow
Skip to content
#

airflow

Here are 768 public repositories matching this topic...

georborodin
georborodin commented Aug 2, 2021

Description

Allow custom executors subclassed from existing (CeleryExecutor, CeleryKubernetesExecutor, etc.) to use default CLI commands to start workers or flower monitoring.

Use case / motivation

Currently, users who decide to roll their own custom Celery-based executor cannot use default commands (i.e. airflow celery worker) even though it's built on top of existing CeleryExe

christopheblin
christopheblin commented Jun 11, 2021

Summary

From an archived workflow, click on "Resubmit" in the UI

The created workflow do not have the appropriate labels

/!\ the bug happens only for archived workflows (when you resubmit a "normal" workflow, the labels are kept)

Be cautious, some labels should not be copied (like workflows.argoproj.io or workflows.argoproj.io/phase)

however, the labels placed manually by the us

akchinSTC
akchinSTC commented Jul 28, 2021

Describe the issue
Current apache helm-chart lists redis as installation enabled but is not actually required when using the kubernetes executor, we should update to false.
https://github.com/elyra-ai/elyra/blob/dcb63e72c12f7e143ca5262f2140a3387f8abd10/etc/kubernetes/airflow/helm/values.yaml#L1420-L1427

To Reproduce

Screenshots or log output
If applicable, add screenshots or l

Improve this page

Add a description, image, and links to the airflow topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the airflow topic, visit your repo's landing page and select "manage topics."

Learn more