Skip to content

fix(mlops): raise when the FeatureGroupManager.update() API call fails - #6443

Open
AkshayShah03 wants to merge 1 commit into
aws:masterfrom
AkshayShah03:fix/feature-group-manager-update-errors
Open

AkshayShah03 wants to merge 1 commit into
aws:masterfrom
AkshayShah03:fix/feature-group-manager-update-errors

Conversation

@AkshayShah03

Copy link
Copy Markdown

Issue #, if available: N/A

Description of changes:

FeatureGroupManager.update() catches every exception from the parent FeatureGroup.update(), which calls UpdateFeatureGroup, logs it, and carries on:

try:
    result = super().update(*args, **kwargs)
except Exception as e:
    logger.error(f"Feature group '{self.feature_group_name}' was not updated successfully: {e}")

The Iceberg property update then still runs, and the method returns self as if the update had succeeded. So ValidationException, ResourceInUse, AccessDenied and similar errors only show up in the logs. The Iceberg branch right below already re-raises after logging.

This change re-raises after logging, so the caller sees the failure and the Iceberg properties aren't changed when the update fails.

Testing:

  • New test_parent_update_failure_is_raised: the ClientError propagates and _update_iceberg_properties isn't called. It fails before this change.
  • tests/unit/sagemaker/mlops/feature_store: 390 passed.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

FeatureGroupManager.update() caught every exception from the parent
FeatureGroup.update() (UpdateFeatureGroup), logged it and carried on: the
Iceberg property update still ran and the method returned self as if the
update had succeeded. ValidationException, ResourceInUse, AccessDenied and
similar errors were therefore only visible in the logs. The Iceberg branch
right below already re-raises after logging.

Re-raise after logging, so the caller sees the failure and the Iceberg
properties are not updated on a failed update.

This branch is waiting to be deployed

1 waiting deployment
manual-approval — 218d8196 Waiting Oct 12, 2026 by AkshayShah03 via wait-for-approval #627
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant