Conversation
Signed-off-by: Ben Wilson <benjamin.wilson@databricks.com>
|
Documentation preview for f4c6422 is available at: Changed Pages (2)
More info
|
There was a problem hiding this comment.
Pull Request Overview
This PR cleans up the Spark MLlib documentation by removing verbose, marketing-style content and simplifying the structure to be more concise and practical.
Key Changes
- Replaced extensive feature descriptions with a concise
FeatureHighlightscomponent showing key capabilities - Condensed multiple sections with redundant information into focused subsections
- Simplified code examples while maintaining technical accuracy
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/docs/classic-ml/traditional-ml/sparkml/index.mdx | Streamlined overview page with concise feature highlights, removed verbose marketing content, and simplified navigation links |
| docs/docs/classic-ml/traditional-ml/sparkml/guide/index.mdx | Condensed comprehensive guide by removing redundant examples and explanations, focusing on essential usage patterns for model logging, deployment formats, datasource autologging, and model registry |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| <TabItem value="pyfunc" label="PyFunc Format"> | ||
|
|
||
| The PyFunc format enables deployment outside of Spark environments: | ||
| Enables deployment without Spark infrastructure: |
There was a problem hiding this comment.
without Spark infrastructure:
this might not be accurate,
it still depends on apache/spark library, and it needs to launch a local mode spark cluster for model inference.
There was a problem hiding this comment.
Yeah I think I need to say "it doesn't need to run IN Spark to work" . I'll update :D Good call out
WeichenXu123
left a comment
There was a problem hiding this comment.
LGTM except one comment
B-Step62
left a comment
There was a problem hiding this comment.
LGTM, can we actually merge 2 pages into one?
Signed-off-by: Ben Wilson <benjamin.wilson@databricks.com>
Signed-off-by: Ben Wilson <benjamin.wilson@databricks.com> Signed-off-by: Tian Lan <sky.blue266000@gmail.com>
🛠 DevTools 🛠
Install mlflow from this PR
For Databricks, use the following command:
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
Remove loads of junk from the SparkML docs
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow should the PR be classified in the release notes? Choose one:
rn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
Yesshould be selected for bug fixes, documentation updates, and other small changes.Noshould be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.What is a minor/patch release?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.