Skip to content
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

Latest update [2.232.2] introduces MLFlow #4885

Open
mathcass opened this issue Oct 4, 2024 · 1 comment
Open

Latest update [2.232.2] introduces MLFlow #4885

mathcass opened this issue Oct 4, 2024 · 1 comment
Labels

Comments

@mathcass
Copy link

mathcass commented Oct 4, 2024

Describe the bug
The latest update to the SageMaker SDK introduces sagemaker-mlflow which then brings in a constellation of dependencies that users might not need. This is a minor change (v2.232.1...v2.232.2) that leads to installing 30 new dependencies.

To reproduce
Install the latest update, pip install sagemaker==2.232.2.

Expected behavior
I would have liked if this release had been included via Python "extras" where you can specify an additional set of installation requirements. For example, rather than installing sagemaker-mlflow automatically, only install it if someone specifies `pip install "sagemaker[mlflow]>=2.232.2".

Screenshots or logs
If applicable, add screenshots or logs to help explain your problem.

System information
A description of your system. Please provide:

  • SageMaker Python SDK version: 2.232.2
  • Framework name (eg. PyTorch) or algorithm (eg. KMeans): N/A
  • Framework version: N/A
  • Python version: N/A
  • CPU or GPU: N/A
  • Custom Docker image (Y/N): N

Additional context
The package could be more usable and leaner if it implemented this as a Python "extra".

@mathcass mathcass added the bug label Oct 4, 2024
@jgangelBLNG
Copy link

jgangelBLNG commented Oct 8, 2024

I also ran into this when a deploy failed unexpectedly. Looks like there was a request to make it optional that wasn't addressed before merge - #4880 (comment)

Edit: mlflow actually puts us over the lambda max deployment size so I'll need to avoid this version entirely until this is made optional

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants