[ML-19342] Fix cross-workspace job source link on databricks#5174
Merged
Conversation
dbczumar
approved these changes
Dec 20, 2021
dbczumar
left a comment
Collaborator
There was a problem hiding this comment.
LGTM! @liangz1 Can we update this test case
mlflow/tests/tracking/context/test_databricks_job_context.py
Lines 21 to 42 in bf63c5d
added 2 commits
December 22, 2021 15:42
Signed-off-by: Liang Zhang <liang.zhang@databricks.com>
dbczumar
reviewed
Dec 23, 2021
Comment on lines
+42
to
+44
| if workspace_url is not None: | ||
| tags[MLFLOW_DATABRICKS_WORKSPACE_URL] = workspace_url | ||
| tags[MLFLOW_DATABRICKS_WORKSPACE_ID] = workspace_id |
Collaborator
There was a problem hiding this comment.
Nit: What if workspace_url is None but workspace_id is not None, and vice versa?
Author
There was a problem hiding this comment.
Yes, it makes sense to not assume that they are dependent on each other.
dbczumar
approved these changes
Dec 23, 2021
dbczumar
left a comment
Collaborator
There was a problem hiding this comment.
re-LGTM with one comment: https://github.com/mlflow/mlflow/pull/5174/files#r774380093
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Liang Zhang liang.zhang@databricks.com
What changes are proposed in this pull request?
Cross-workspace job source link and notebook source link are incorrect because it does not use the workspace URL and workspace ID that the job/notebook is executed on, but uses it's own workspace URL and workspace ID. This PR fixes them by using the logged correct workspace URL and workspace ID.
How is this patch tested?
Unit test: existing test fixed.
Does this PR change the documentation?
ci/circleci: build_doccheck. If it's successful, proceed to thenext step, otherwise fix it.
Detailson the right to open the job page of CircleCI.Artifactstab.docs/build/html/index.html.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/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