Skip to content

feature: Feat: Feature Store in Sagemaker SDK v3 (5496)#5717

Draft
aviruthen wants to merge 1 commit intoaws:masterfrom
aviruthen:feature/feat-feature-store-in-sagemaker-sdk-v3-5496-2
Draft

feature: Feat: Feature Store in Sagemaker SDK v3 (5496)#5717
aviruthen wants to merge 1 commit intoaws:masterfrom
aviruthen:feature/feat-feature-store-in-sagemaker-sdk-v3-5496-2

Conversation

@aviruthen
Copy link
Copy Markdown
Collaborator

Description

Feature Store functionality ALREADY EXISTS in SDK V3 within the sagemaker-mlops package at sagemaker.mlops.feature_store. The issue is a documentation/discoverability gap — users migrating from V2 (sagemaker.feature_store) cannot find Feature Store in V3 because: (1) the namespace changed from sagemaker.feature_store to sagemaker.mlops.feature_store, (2) the migration.md only has a single row mentioning Feature Store without detailed guidance, (3) the README.md for sagemaker-mlops doesn't mention Feature Store at all, and (4) there's a detailed MIGRATION_GUIDE.md inside the feature_store directory but it's not referenced from any top-level documentation. The V3 Feature Store is fully implemented with: FeatureGroup (re-exported from sagemaker-core), feature definitions, ingestion manager, Athena queries, dataset builder, feature processor, and all associated enums/utilities. The fix requires documentation improvements across multiple files to make Feature Store discoverable.

Related Issue

Related issue: 5496

Changes Made

  • sagemaker-mlops/src/sagemaker/mlops/__init__.py
  • sagemaker-mlops/README.md
  • migration.md
  • docs/sagemaker_core/index.rst
  • sagemaker-mlops/tests/unit/sagemaker/mlops/feature_store/test_feature_store_init.py

AI-Generated PR

This PR was automatically generated by the PySDK Issue Agent.

  • Confidence score: 85%
  • Classification: type: feature request
  • SDK version target: V3

Merge Checklist

  • Changes are backward compatible
  • Commit message follows prefix: description format
  • Unit tests added/updated
  • Integration tests added (if applicable)
  • Documentation updated (if applicable)

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