0. Grant yourself read access to Kumo tables
Because Kumo may create new tables or update existing ones during prediction runs, grant yourself (or a reader role) access to existing and future tables in the destination schema.Replace placeholders:
TARGET_DB / TARGET_SCHEMA
→ where your BP writes prediction/output tablesMY_ROLE
→ the role you use to read those outputs (can beACCOUNTADMIN
, or any role)
1. Define Procedures
Create two small procedures you can call from the notebook to safely start and stop the Kumo app.Replace:
MY_DB.MY_SCHEMA
→ where to store these procedures (e.g.,KUMO.AUTOMATION
)MY_APP
→ your installed app name (e.g.,KUMO_SPCS_RELEASE_INTERNAL
)MY_USER_SCHEMA
→ schema used when installing the app
2. Use these in your Kumo BP SDK snippet
If you haven’t set up the SDK yet, follow the setup guide hereRules:
- Call START_APP() first (very first command).
- Run your BP pipeline with non_blocking = False so the notebook waits for completion.
- Call STOP_APP() last (very last command), so the app shuts down after the job.
Example notebook flow
SQL cell — start app (first line):3) Schedule the Containerized Notebook
- Open your containerized notebook in Snowflake.
- Click Schedule.
- Set your CRON/time zone and save
- Every 3 hours (top of hour):
USING CRON 0 */3 * * * America/Chicago
- Daily at 7:00 AM:
USING CRON 0 7 * * * America/Chicago
- Daily at 8:00 PM:
USING CRON 0 20 * * * America/Chicago