Fix the Model Validation#131
Merged
Merged
Conversation
arpitjasa-db
reviewed
Jan 8, 2024
arpitjasa-db
left a comment
Contributor
There was a problem hiding this comment.
Thanks for the changes @qili86 ! Would you mind generating a Stacks repo from your local branch and adding screenshots of the validation workflow working as well?
Contributor
Author
@arpitjasa-db I generated the stack repo "test_mv" from my local branch, and the model validation part is now working fine without error |
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.

Current default template for Model Validation part fails because of the two errors below:
error_1.
The full error msg is below:
Validation failed : API request to list files under path `` failed with status code 400. Response body: {"error_code":"INVALID_PARAMETER_VALUE","message":"Invalid name 'local_dev.custom_project.custom_project_model'. A workspace registered model name must be a non-empty UTF-8 string and cannot contain forward slashes(/), periods(.), or colons(:). If trying to access models in the Unity Catalog, make sure to install version 2.4.1 or above of the MLflow Python client, then configure the MLflow client to access models in Unity Catalog via mlflow.set_registry_uri('databricks-uc') before accessing models."}
Fix to error_1: add "mlflow.set_registry_uri('databricks-uc')"
error_2:
Fix to error_2: change to "fare_amount" which is the correct prediction target