-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[ML] Adds created_by job property for the advanced wizard #167021
[ML] Adds created_by job property for the advanced wizard #167021
Conversation
Pinging @elastic/ml-ui (:ml) |
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
@@ -240,7 +241,12 @@ export async function cloneJob(jobId) { | |||
return; | |||
} | |||
|
|||
if (cloneableJob !== undefined && originalJob?.custom_settings?.created_by !== undefined) { | |||
const createdBy = originalJob?.custom_settings?.created_by; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I export jobs, looks like created_by
is removed (tried an advanced job and a multi-metric one). I can't remember - was this intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're using the flag exclude_generated: true
when retrieving the jobs from es. This removes the created_by
prop.
If we think it would be better to not strip this out, I can change it in a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds a good idea to retain created_by
on export, and to do it in a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and LGTM.
As discussed, let's retain the created_by
field on export in a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM ⚡
…167319) When exporting an anomaly detection job, it would be useful if the original `created_by` property was not removed from the job config. Related to #167021 (comment) Related PR #88898
Adds
created_by
property ofadvanced-wizard
to all jobs created by the advanced job wizard.Previously no
created_by
property was added to these jobs.When cloning, jobs with no
created_by
property or one with a value ofadvanced-wizard
will be opened in the advanced wizard.Closes #166053