19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
#ask-community
Title
# ask-community
j
Jake Kagan
01/18/2023, 10:55 PMquestion for you guys about passing jobs and schedules and other stuff..
let's say i have a bunch of schedules, each one is listed in the jobs directory
__init____init__ Copy code
from .jobs.__init__ import jobs, schedules
from dagster import Definitions
def scheduler(schedules: dict):
for schedule_name, schedule_config in schedules.items():
# set each schedule_name as a variable with the value of schedule_config
# should i use exec/globals? or is there a dagster solution that is not as risky??
jobs = Definitions(jobs=[*jobs])
scheduler(schedules) --> schedule_1 = ScheduleDefinition1
schedule_2 = ScheduleDefinition2D 1
c
chris
01/19/2023, 12:01 AMjust a note that you don’t need to import .jobs.__init, just regular .jobs should work
what is the scheduler function supposed to do here exactly?
Having trouble parsing what you’re looking to get out of doing exactly
j
Jake Kagan
01/19/2023, 12:10 AMhey thanks, so basically within jobs i have a bunch of subdirectories, each one has a file or a few that end up being a job. and then i have another folder that holds other types of jobs, also having subdirectories. so my goal is to funnel all those jobs into the top-level
__init__doing so with jobs seems to be easy, but the schedules are tough because each one is it's variable
Copy code
from dagster import ScheduleDefinition
from .usage_from_bigq.usage_from_bigq import namea
from .usage_from_bigq.job_test import nameb
jobs = [namea, nameb]
schedules = {"basic_schedule": ScheduleDefinition(job=namea, cron_schedule="0 0 * * *", execution_timezone="US/Pacific")} Copy code
from .jobs.__init__ import jobs, schedules
from .jobs2.__init__ import jobs as jobs2, schedules as schedules2
from dagster import Definitions
jobs = Definitions(jobs=[*jobs, *jobs2])basically id like to keep the job definitions and the schedules at the job level
c
chris
01/19/2023, 12:19 AMI’m having trouble parsing the code examples you sent, is the one where you’re defining schedules living in some subdirectory and the one defining
Definitionsare you saying that including schedules as a dictionary is causing the problem? If so, what problem is it causing exactly?
also, what is schedule config here? There’s no concept of configuring schedules to my knowledge in dagster
j
Jake Kagan
01/19/2023, 12:26 AMsorry for being confusing - im definitely not great at this!
let's say i have three files:
1. a job file
2. the job directory (one of a few) with an
__init____init__i just got it from here
c
chris
01/19/2023, 12:27 AMah i see - since they need to import jobs
and you’ve tried including schedules in their own subdirectory?
j
Jake Kagan
01/19/2023, 12:27 AMyeah the dict was gonna hold a bunch of schedules...and then i was gonna make them global variables??
yeah nothing works unless its instantiated at the top init
c
chris
01/19/2023, 12:28 AMWhat error are you getting? You might need to do an editable install of the module and change away fro doing relative imports
j
Jake Kagan
01/19/2023, 12:28 AMim actually not getting an error lol...its just not showing up
c
chris
01/19/2023, 12:29 AMah wait are you including the schedules in the
Definitionsthats what defines what shows up in dagit
Definitions(schedules=…, …j
Jake Kagan
01/19/2023, 12:30 AMok i did not include that!
but still need to include a list of variables as an argument to that
oh wow..this works:
schedules = [ScheduleDefinition(job=namea, cron_schedule="0 0 * * *", execution_timezone="US/Pacific")] Copy code
jobs = Definitions(jobs=[*jobs],
schedules=[*schedules])i just added a
name=c
chris
01/19/2023, 12:34 AMyup!
j
Jake Kagan
01/19/2023, 12:34 AM🙏
you are awesome man
c
chris
01/19/2023, 12:34 AMjust doin my job 🫡
🌈 1
keep sql’ing
🤣 1