-
Notifications
You must be signed in to change notification settings - Fork 137
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
Week 3 Project Submission #53
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ianyoung great work, well done!
week_3/project/week_3.py
Outdated
yield RunRequest( | ||
run_key=new_file, | ||
run_config={ | ||
"resources": {**docker["resources"]}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ianyoung I did exactly the same as you:) However, the code can be simplified as
{**docker, "ops": {"get_s3_data": {"config": {"s3_key": new_file}}},
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point @yjw868. Now updated. Thanks!
We can copy the full config settings and override only the relevant parts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, expect for the second sensors (See comment) 👍
week_3/project/week_3.py
Outdated
|
||
docker_week_3_schedule = None # Add your schedule | ||
# Schedule for docker: Start of every hour | ||
docker_week_3_schedule = ScheduleDefinition(job=docker_week_3_pipeline, cron_schedule="0 * * * *") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code passes the tests, but I believe this definition is incorrect. Try to turn o this schedule in Dagit, and it will compain about incorrect configuration. See this discussion - https://data-orchestration.slack.com/archives/C03SB6TAXQV/p1661960430498179
Summary of changes:
Confirmed all tests passing.