-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Adds job_id parameter. #3850
Adds job_id parameter. #3850
Conversation
…dence over job_id generated from job_id_prefix.
Check out this pull request on Review Jupyter notebook visual diffs & provide feedback on notebooks. Powered by ReviewNB |
Hi @AndrewLeach. Thanks for your PR. I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
/test kubeflow-pipeline-frontend-test |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Ark-kun The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
/retest |
* Adds job_id parameter to ml_engine train component, which takes precedence over job_id generated from job_id_prefix. * Restores ipynb config. Co-authored-by: andrewleach <andrewleach@google.com>
Fixes kubeflow#4430 The issue was introduced in kubeflow#3850. That PR has added a new parameter in the middle of the the create_job function signature which can cause breaking changes as the parameter ordering changes.
…ixes #4430 (#4432) * Components - Fixed the GCP - ML Engine - Batch predict component Fixes #4430 The issue was introduced in #3850. That PR has added a new parameter in the middle of the the create_job function signature which can cause breaking changes as the parameter ordering changes. * Fixed test
* Adds job_id parameter to ml_engine train component, which takes precedence over job_id generated from job_id_prefix. * Restores ipynb config. Co-authored-by: andrewleach <andrewleach@google.com>
…ixes kubeflow#4430 (kubeflow#4432) * Components - Fixed the GCP - ML Engine - Batch predict component Fixes kubeflow#4430 The issue was introduced in kubeflow#3850. That PR has added a new parameter in the middle of the the create_job function signature which can cause breaking changes as the parameter ordering changes. * Fixed test
Adds job_id parameter to ml_engine train component.