-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
registry.html points to model-registry.html #2232
Merged
Merged
Conversation
This file contains 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
fixes #2165 |
smurching
approved these changes
Dec 19, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
smurching
approved these changes
Dec 19, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
smurching
pushed a commit
that referenced
this pull request
Dec 20, 2019
* registry.html points to model-registry.html
amrqt
added a commit
to criteo-forks/mlflow
that referenced
this pull request
Dec 20, 2019
* Replace ValueError check with Exception check for JSON.loads in HTTP requests (mlflow#2204) * Replace ValueError check with Exception check for JSON.loads in HTTP requests When an HTTP request is executed, it tries to parse an error response as JSON. This check only handles ValueError. `json.loads` can throw multiple types of errors and is not specific about which. Therefore, I've switched to catch the `Exception`. * Add killed status constraint (mlflow#2110) * Add killed status constraint * Fix migration script * Do migration only if check constraints are defined * Use alter_column to replace constraints * Apply previous constraints with the table_args arguments * Specify `native_enum=False` * Update tests * Update sql latest schema * relaunch travis * relaunch travis * Fix mlflow.keras.save_model with DBFS (mlflow#2216) Fixed a bug where mlflow.keras.save_model failed against "/dbfs/..." paths due to the lack of support for random writes when using DBFS FUSE. * Fix handling of empty directories in fs based artifact repositories. (mlflow#1891) * Fix handling of empty directories in artifact filesystem based artifact repositories. * Fixed tests. * Update. * Update. * nits * nit * Fix python27 compatibility. * fix * Fix download artifacts behavior and minor bug in s3 repo behavior. * Removed debug print. * Updated test. * Updated test for local artifact repo. * nit * nit: Removed outdated comment. * Fix artifact URI constructions in FileStore and SqlAlchemyStore (mlflow#2221) * append_uri_to_path with tons of tests * Store changes with test cases * Test multi-arg path * Lint * docs casing * Revert * Docstring * Add Java implementation of Spark datasource autologging (mlflow#2181) Adds Java implementation of Spark datasource autologging as described in https://docs.google.com/document/d/11nhwZtj-rps0stxuIioFBM9lkvIh_ua45cAFy_PqdHU/edit under a new mlflow-spark maven package. The current implementation notifies subscribers with datasource path, version, and format information. A follow-up PR will add logic to register a subscriber from Python when mlflow.spark.autolog() is called. * registry.html points to model-registry.html (mlflow#2232) * registry.html points to model-registry.html * 1.5 Changelog Changes (mlflow#2231) Add changelog for MLflow 1.5 Co-authored-by: Andy Chow <58712524+andychow-db@users.noreply.github.com> Co-authored-by: Jean-Denis Lesage <jdlesage@gmail.com> Co-authored-by: tomasatdatabricks <33237569+tomasatdatabricks@users.noreply.github.com> Co-authored-by: dbczumar <39497902+dbczumar@users.noreply.github.com> Co-authored-by: Siddharth Murching <smurching@gmail.com> Co-authored-by: Mani Parkhe <mani@databricks.com> Co-authored-by: juntai-zheng <39497939+juntai-zheng@users.noreply.github.com>
lorenzwalthert
pushed a commit
to lorenzwalthert/mlflow
that referenced
this pull request
Jan 4, 2020
* registry.html points to model-registry.html
avflor
pushed a commit
to avflor/mlflow
that referenced
this pull request
Aug 22, 2020
* registry.html points to model-registry.html
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.
What changes are proposed in this pull request?
Create a new
registry.rst
that points tomodel-registry.rst
How is this patch tested?
make livehtml
only one link shows up on
index.html
cc: @clemens-db, @stbof
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) does this PR affect?
How 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