Enable --serve-artifacts by default#6502
Conversation
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
dbczumar
left a comment
There was a problem hiding this comment.
Two small pieces of feedback:
- When I run with
--backend-store-uri sqlite:///mydb.sqlite --no-serve-artifactsand forget to specify `--default-artifact-root, I see:
mlflow server --backend-store-uri sqlite:///mydb.sqlite --no-serve-artifacts
Option 'default-artifact-root' is required when backend store is not local file based.
Usage: mlflow server [OPTIONS]
Try 'mlflow server --help' for help.
Error: Option 'default-artifact-root' is required when backend store is not local file based.
Can we update this to say that 'default-artifact-root' is required when backend store is not local file based and artifact serving is disabled?
- Do we need to update docs, such as https://mlflow.org/docs/latest/tracking.html#using-the-tracking-server-for-proxied-artifact-access, to indicate that proxied artifact access is enabled by default and also talk about how the
--no-serve-artifactsoption can be used to opt out?
Got it, thanks for the catch!
We do :) I'll update them. |
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
docs/source/tracking.rst
Outdated
| .. code-block:: bash | ||
| :caption: Command to run the tracking server in this configuration | ||
|
|
||
| mlflow server --backend-store-uri file::///path/to/mlruns --no-serve-artifacts |
There was a problem hiding this comment.
Separated the command from the image to make it easier to edit and copy.
There was a problem hiding this comment.
Fantastic!
| .. code-block:: bash | |
| :caption: Command to run the tracking server in this configuration | |
| mlflow server --backend-store-uri file::///path/to/mlruns --no-serve-artifacts | |
| .. code-block:: bash | |
| :caption: Command to run the tracking server in this configuration | |
| mlflow server --backend-store-uri file:///path/to/mlruns --no-serve-artifacts |
docs/source/tracking.rst
Outdated
| .. code-block:: bash | ||
| :caption: Command to run the tracking server in this configuration | ||
|
|
||
| mlflow server --backend-store-uri postgresql:://URI --default-artifact-root s3://bucket_name --host remote_host --no-serve-artifacts |
There was a problem hiding this comment.
I think we should remove the double colons in these examples, right?
| mlflow server --backend-store-uri postgresql:://URI --default-artifact-root s3://bucket_name --host remote_host --no-serve-artifacts | |
| mlflow server --backend-store-uri postgresql://URI --default-artifact-root s3://bucket_name --host remote_host --no-serve-artifacts |
There was a problem hiding this comment.
Can we also replace URI with a realistic example?
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy <[email protected]>
Signed-off-by: harupy [email protected]
Related Issues/PRs
#xxx
What changes are proposed in this pull request?
Enable
--serve-artifactsby default when running a tracking server.How is this patch tested?
Does this PR change the documentation?
Detailslink on thePreview docscheck.Release Notes
Is this a user-facing change?
(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts: Artifact stores and artifact loggingarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesarea/examples: Example codearea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models: MLmodel format, model serialization/deserialization, flavorsarea/pipelines: Pipelines, Pipeline APIs, Pipeline configs, Pipeline Templatesarea/projects: MLproject format, project running backendsarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra: MLflow Tracking server backendarea/tracking: Tracking Service, tracking client APIs, autologgingInterface
area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows: Windows supportLanguage
language/r: R APIs and clientslanguage/java: Java APIs and clientslanguage/new: Proposals for new client languagesIntegrations
integrations/azure: Azure and Azure ML integrationsintegrations/sagemaker: SageMaker integrationsintegrations/databricks: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" 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 notes