You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a tips for anyone who try to automate sqlmesh command with prefect, set MAX_FORK_WORKERS into 1 in your prefect deployment. It is due to sqlmesh is defaulted to use parallel loading when in linux env, and somehow that didn't works with prefect task that are executed inside a child process too. Setting the value into 1 will disable this sqlmesh behaviour
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Just a tips for anyone who try to automate sqlmesh command with prefect, set MAX_FORK_WORKERS into 1 in your prefect deployment. It is due to sqlmesh is defaulted to use parallel loading when in linux env, and somehow that didn't works with prefect task that are executed inside a child process too. Setting the value into 1 will disable this sqlmesh behaviour
reference: https://sqlmesh.readthedocs.io/en/stable/reference/configuration/?h=max+fork+workers#parallel-loading
Beta Was this translation helpful? Give feedback.
All reactions