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
{{ message }}
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
I'm wondering why does not pinball save current jobs metadata to mysql? For now current jobs metadata is loaded in the parser layer when the workflow is scheduled. This concept is hard to pass definition of workflow with extra params through UI. Is there a reason?
#TODO(mao): to make it flexible that allow users specify through UI
https://github.com/pinterest/pinball/blob/master/pinball/parser/repository_config_parser.py#L121
FYI. I always thank you for making good workflow solution. Recently I implemented backfilling form for specific requrement of my company.
The text was updated successfully, but these errors were encountered:
I think it's to make sure we always have the latest version of the code (includes job/workflow metadata), the job/workflow code in the repo is always the ground truth.
Can you describe your use case that needs to pass extra args through UI?
Thanks,
Changshu
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm wondering why does not pinball save current jobs metadata to mysql? For now current jobs metadata is loaded in the parser layer when the workflow is scheduled. This concept is hard to pass definition of workflow with extra params through UI. Is there a reason?
FYI. I always thank you for making good workflow solution. Recently I implemented backfilling form for specific requrement of my company.
The text was updated successfully, but these errors were encountered: