Add core tensorflow 2.x api example to mlflow/examples #8235
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
github-actions
bot
added
area/examples
|
@dheerajnbhat Thank you for the contribution! Could you fix the following issue(s)? ⚠ DCO checkThe DCO check failed. Please sign off your commit(s) by following the instructions here. See https://github.com/mlflow/mlflow/blob/master/CONTRIBUTING.md#sign-your-work for more details. |
|
Documentation preview for 2603808 will be available here when this CircleCI job completes successfully. More info
|
Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
harupy
reviewed
Apr 19, 2023
harupy
reviewed
Apr 19, 2023
harupy
reviewed
Apr 19, 2023
harupy
reviewed
Apr 19, 2023
harupy
reviewed
Apr 19, 2023
harupy
reviewed
Apr 19, 2023
harupy
reviewed
Apr 19, 2023
harupy
reviewed
Apr 19, 2023
|
@dheerajnbha thanks for the PR, left some comments! |
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
|
Hi @harupy, I have updated as per your comments. Can you review the changes made? |
harupy
reviewed
Apr 19, 2023
harupy
reviewed
Apr 19, 2023
harupy
reviewed
Apr 19, 2023
harupy
reviewed
Apr 19, 2023
harupy
reviewed
Apr 19, 2023
harupy
approved these changes
Apr 20, 2023
harupy
reviewed
Apr 20, 2023
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
mlflow depends on pandas, so removing pandas dependency Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
harupy
reviewed
Apr 20, 2023
harupy
reviewed
Apr 20, 2023
harupy
reviewed
Apr 20, 2023
Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
mlflow depends on pandas Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
harupy
reviewed
Apr 20, 2023
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
harupy
reviewed
Apr 20, 2023
Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Dheeraj Bhat <dheerajnbhat@gmail.com>
|
@dheerajnbhat Merged, thanks for the PR! |
Glad to contribute to mlflow :) |
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.
Related Issues/PRs
Resolve #8049 - Add Core TensorFlow Example to mlflow/examples
What changes are proposed in this pull request?
Added core tensorflow 2.x api example to mlflow/examples
How is this patch tested?
Does this PR change the documentation?
Modified tensorflow version in examples/README.md
Release Notes
Is this a user-facing change?
Add usage examples for
mlflow.tensorflowAPIs for tensorflow 2.xWhat 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/recipes: Recipes, Recipe APIs, Recipe configs, Recipe 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