You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> **MLflow 2.0 advisory**: For MLflow versions earlier than 2.0, use the `MlflowClient.list_registered_models()` method instead.
114
+
> For MLflow versions earlier than 2.0, use the `MlflowClient.list_registered_models()` method instead.
115
115
116
116
### Get specific model versions
117
117
@@ -144,7 +144,7 @@ To understand the differences between the functions `mlflow.<flavor>.load_model(
144
144
MLflow supports stages for a model to manage the model lifecycle. The model version can transition from one stage to another. Stages are assigned to specific versions for a model. A model can have multiple versions on different stages.
145
145
146
146
> [!IMPORTANT]
147
-
> Stages can be accessed only by using the MLflow SDK. They aren't visible in the [Azure Machine Learning studio](https://ml.azure.com). They can't be retrieved by using the Azure Machine Learning SDK, the Azure Machine Learning CLI, or the Azure Machine Learning REST API. Deployment from a specific model stage isn't currently supported.
147
+
> Stages can be accessed only by using the MLflow SDK. They aren't visible in the [Azure Machine Learning studio](https://ml.azure.com). Stages can't be retrieved by using the Azure Machine Learning SDK, the Azure Machine Learning CLI, or the Azure Machine Learning REST API. Deployment from a specific model stage isn't currently supported.
Multiple model versions can be in the same stage at the same time in MLflow. In the previous example, the method returns the latest version (most recently published) among all versions for the stage.
164
164
165
165
> [!IMPORTANT]
166
-
> When you work with the MLflow SDK, keep in mind that stage names are case sensitive.
166
+
> In the MLflow SDK, stage names are case sensitive.
167
167
168
168
### Transition models
169
169
@@ -197,7 +197,7 @@ model = mlflow.pyfunc.load_model(f"models:/{model_name}/Staging")
197
197
198
198
Editing registered models is supported in both MLflow and Azure Machine Learning, but there are some important differences. The following sections describe some options.
199
199
200
-
> [!WARNING]
200
+
> [!NOTE]
201
201
> Renaming models isn't supported in Azure Machine Learning because model objects are immmutable.
202
202
203
203
### Edit model description and tags
@@ -256,11 +256,11 @@ The MLflow client exposes several methods to retrieve and manage models. The fol
256
256
257
257
Table footnotes:
258
258
259
-
-**1** Use Uniform Resource Identifiers (URIs) with the format `runs:/<ruin-id>/<path>`.
260
-
-**2** Use URIs with the format `azureml://jobs/<job-id>/outputs/artifacts/<path>`.
261
-
-**3** Registered models are immutable objects in Azure Machine Learning.
262
-
-**4** Use the search box in Azure Machine Learning studio. Partial matching is supported.
263
-
-**5** Use [registries](how-to-manage-registries.md) to move models across different workspaces and preserve lineage.
259
+
-1: Use Uniform Resource Identifiers (URIs) with the format `runs:/<ruin-id>/<path>`.
260
+
-2: Use URIs with the format `azureml://jobs/<job-id>/outputs/artifacts/<path>`.
261
+
-3: Registered models are immutable objects in Azure Machine Learning.
262
+
-4: Use the search box in Azure Machine Learning studio. Partial matching is supported.
263
+
-5: Use [registries](how-to-manage-registries.md) to move models across different workspaces and preserve lineage.
0 commit comments