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

[Task]: Expand Airflow DAG documentation #2777

Closed
everton137 opened this issue Mar 24, 2023 · 0 comments · Fixed by #2926
Closed

[Task]: Expand Airflow DAG documentation #2777

everton137 opened this issue Mar 24, 2023 · 0 comments · Fixed by #2926
Assignees
Labels
Milestone

Comments

@everton137
Copy link

everton137 commented Mar 24, 2023

What needs to happen?

My team is likely going to use Apache Airflow as our task scheduler. I am aware we already have one DAG example in the official documentation, but I was wondering if some best practice or real case scenarios could be shared.

I've started to play around with the Docker version of Airflow, but its docker-compose YAML file seems to be an overkill. I made an Airflow tutorial where Redis and Celery Flower are removed.

Some cases that could be added in the documentation:

  • In case we have several Hop workflows, do we create a DAG for each workflow? Or we add as tasks in the same DAG? I am planning to use the DockerOperator.
  • How is your docker-compose YAML file?
  • How to pass Hop parameters to Airflow parameters?

These are a few questions that came to my mind after a quick discussion with @bamaer in the Hop chat.

Issue Priority

Priority: 2

Issue Component

Component: Documentation

@github-actions github-actions bot added P1 Critical Issue Documentation labels Mar 24, 2023
@hansva hansva added P2 Default Priority and removed P1 Critical Issue labels Mar 24, 2023
@hansva hansva changed the title [Task]: [Task]: Expand Airflow DAG documentation Mar 24, 2023
@bamaer bamaer self-assigned this Mar 31, 2023
bamaer added a commit to bamaer/hop that referenced this issue May 13, 2023
@hansva hansva added this to the 2.5 milestone May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants