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 }}
Repository navigation
Commit 7c37579
Browse filesBrowse the repository at this point in the historyBrowse files
fix(model-monitor): honor base_job_name for job definition names (#6373)
ModelMonitor subclasses generated the monitoring job definition name from
the type's JOB_DEFINITION_BASE_NAME constant, ignoring a user-supplied
base_job_name -- even though the monitoring schedule name already honors it.
As a result base_job_name was silently dropped for the job definition (and
the monitoring resources derived from it).
Add a _generate_job_definition_name() helper on the ModelMonitor base
(mirroring _generate_monitoring_schedule_name) that uses base_job_name when
provided and falls back to JOB_DEFINITION_BASE_NAME otherwise, and use it in
the data-quality, model-quality, model-bias and model-explainability create
and update paths.
Also make the four *_update_failure tests deterministic: they asserted the
regenerated job definition name differs from the original, which relied on
two name_from_base calls landing in different milliseconds (flaky on master).
Patch name_from_base with a counter-based unique name in those tests.
Note: the recurring execution processing job names are assigned by the
SageMaker service and remain non-customizable.
Relates-to #4783
Co-authored-by: Roja Reddy Sareddy <rsareddy@amazon.com>
0 commit comments