-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Add ability to add features to existing feature groups in Sagemaker #26809
Comments
looking into this |
@DrFaust92 just wanted to see if you were able to make any progress on this? |
@xianwill im looking into this but unfortunately this proved to not as trivial as removal of features requires recreate and i wasnt able to make this work properly in my tests. if anyone wants to take a crack at this i can unassign myself as this is not a top priority ticket for me. |
@DrFaust92 I have started looking at the issue, however, similarly, struggle to make Terraform force changes in case if the list of feature definitions change simultaneously with giving the ability to add new features. Can you share some of your work so I could have a sneak peek on potential solutions? |
Any update on this? Full recreation limits use of this resource since all data stored in the feature also gets deleted. |
Any updates on getting a release with this support? |
Community Note
Description
Currently when one adds new feature to the existing Sagemaker feature group, it forces the destruction of resource. However, since FeatureAdditions functionality has been introduced to the UpdateFeatureGroup API call, this must not be the case.
New or Affected Resource(s)
Potential Terraform Example
Expected Behavior
When adding a feature to feature group, the feature group should be updated with the new feature.
Actual Behavior
Executing Terraform plan gives the following:
References
The text was updated successfully, but these errors were encountered: