Remove shap as core dependency

[jmahlik]

Related Issues/PRs

Closes #7681

What changes are proposed in this pull request?

Moving shap to an extra and gating the shap tab in recipes behind shap being installed. This was the one place I could find with a hard dependency on shap. Happy to make other adjustments if there are places that were missed.

This likely can be classed as a bug fix. I'm not sure if it would be considered a breaking change, since users will have to install mlflow and manage the shap install separately. It should for sure be mentioned in the release notes.

How is this patch tested?

Tested most of the relevant functionality without shap installed on 3.11. It's quite hard to run the full test suite on Windows/3.11 since some of the extra ml requirements are not readily installable.

• Existing unit/integration tests
• New unit/integration tests
• Manual tests (describe details, including test results, below)

Does this PR change the documentation?

• No. You can skip the rest of this section.
• Yes. Make sure the changed pages / sections render correctly in the documentation preview.

Release Notes

Is this a user-facing change?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

Move shap to an extra ml requirement to improve python 3.11 compatibility. Shap needs to be installed separately for the shap functionality in autologging/recipies.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/artifacts: Artifact stores and artifact logging
• area/build: Build and test infrastructure for MLflow
• area/docs: MLflow documentation pages
• area/examples: Example code
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/recipes: Recipes, Recipe APIs, Recipe configs, Recipe Templates
• area/projects: MLproject format, project running backends
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/server-infra: MLflow Tracking server backend
• area/tracking: Tracking Service, tracking client APIs, autologging

Interface

• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
• area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
• area/windows: Windows support

Language

• language/r: R APIs and clients
• language/java: Java APIs and clients
• language/new: Proposals for new client languages

Integrations

• integrations/azure: Azure and Azure ML integrations
• integrations/sagemaker: SageMaker integrations
• integrations/databricks: Databricks integrations

How should the PR be classified in the release notes? Choose one:

• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

[mlflow-automation]

Documentation preview for 57fd4d8 will be available here when this CircleCI job completes successfully.

More info

• Ignore this comment if this PR does not change the documentation.
• It takes a few minutes for the preview to be available.
• The preview is updated when a new commit is pushed to this PR.
• This comment was created by https://github.com/mlflow/mlflow/actions/runs/4724545380.

[jmahlik]

I'll fix up the failing tests. Would it be worth adding a ci test against python 3.11 at all?

[jmahlik]

Landed on installing shap for the tests vs. removing it entirely and checking the for error logs. That seems to make more sense.

[BenWilson2]

LGTM! Thanks for the contribution @jmahlik :)

[BenWilson2]

@sunishsheth2009 any objections to having a card not populated so that we don't have to have shap as a hard dependency?

[sunishsheth2009]

@sunishsheth2009 any objections to having a card not populated so that we don't have to have shap as a hard dependency?

I think this makes sense. Maybe we should add it here in that case: https://github.com/mlflow/recipes-examples/blob/main/requirements.txt

[jmahlik]

Rebased to resolve the conflict.

[jmahlik]

Looks like some possibly flakey tests failing for 404's on installing pyspark and mlleap serialization.

[BenWilson2]

@jmahlik those test failures were due to the release of PySpark3.4 and a recent breaking release of mlserver. They've been fixed in master. :)

[jmahlik]

Rebased.

[BenWilson2]

Thanks for another great contribution @jmahlik 🎉