Skip to content

Commit 88508d7

Browse files
authored
Update articles/machine-learning/how-to-use-mlflow-azure-databricks.md
1 parent 88bbb40 commit 88508d7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/machine-learning/how-to-use-mlflow-azure-databricks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -184,7 +184,7 @@ Models are logged inside of the run being tracked. That means that models are av
184184

185185
As opposite to tracking, **model registries can't operate** at the same time in Azure Databricks and Azure Machine Learning. Either one or the other has to be used. By default, the Azure Databricks workspace is used for model registries; unless you chose to [set MLflow Tracking to only track in your Azure Machine Learning workspace](#set-mlflow-tracking-to-only-track-in-your-azure-machine-learning-workspace), then the model registry is the Azure Machine Learning workspace.
186186

187-
Then, considering you are using the default configuration, the following line will log a model inside the corresponding runs of both both Azure Databricks and Azure Machine Learning, but it will register it only on Azure Databricks:
187+
Then, considering you are using the default configuration, the following line will log a model inside the corresponding runs of both Azure Databricks and Azure Machine Learning, but it will register it only on Azure Databricks:
188188

189189
```python
190190
mlflow.spark.log_model(model, artifact_path = "model",

0 commit comments

Comments
 (0)