[ML] Adds created_by job property for the advanced wizard#167021
Conversation
jgowdyelastic
added
release_note:enhancement
:ml
Feature:Anomaly Detection
|
Pinging @elastic/ml-ui (:ml) |
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
| } | ||
|
|
||
| if (cloneableJob !== undefined && originalJob?.custom_settings?.created_by !== undefined) { | ||
| const createdBy = originalJob?.custom_settings?.created_by; |
There was a problem hiding this comment.
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.
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.
Sounds a good idea to retain created_by on export, and to do it in a separate PR.
peteharverson
left a comment
peteharverson
left a comment
There was a problem hiding this comment.
Tested and LGTM.
As discussed, let's retain the created_by field on export in a separate PR.
…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
szabosteve
changed the title
6 participants
Adds
created_byproperty ofadvanced-wizardto all jobs created by the advanced job wizard.Previously no
created_byproperty was added to these jobs.When cloning, jobs with no
created_byproperty or one with a value ofadvanced-wizardwill be opened in the advanced wizard.Closes #166053