Improve HuggingFace dataset logging #9845
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
|
Documentation preview for b66b130 will be available here when this CircleCI job completes successfully. More info
|
chenmoneygithub
force-pushed
the
fix-hf-dataset
branch
from
0cfc117 to
4597ff9
Compare
github-actions
bot
added
area/tracking
Signed-off-by: chenmoneygithub <[email protected]>
chenmoneygithub
force-pushed
the
fix-hf-dataset
branch
from
4597ff9 to
3331845
Compare
Signed-off-by: chenmoneygithub <[email protected]>
BenWilson2
reviewed
Oct 6, 2023
chenmoneygithub
force-pushed
the
fix-hf-dataset
branch
from
63289f0 to
c585332
Compare
Co-authored-by: Ben Wilson <[email protected]> Signed-off-by: Chen Qian <[email protected]>
chenmoneygithub
force-pushed
the
fix-hf-dataset
branch
from
c585332 to
b66b130
Compare
BenWilson2
added a commit
that referenced
this pull request
Oct 24, 2023
Signed-off-by: chenmoneygithub <[email protected]> Signed-off-by: Chen Qian <[email protected]> Co-authored-by: Ben Wilson <[email protected]>
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
#xxxWhat changes are proposed in this pull request?
A few things:
taskargument since it's deprecated and we are in experimental phase. Please refer to HF's doc.datasets.load_dataset(), and call out users need to specify the exact path.load()method, if the same key appears both inkwargsand the instance itself, raise an error instead of silent overwriting.How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing 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/gateway: AI Gateway service, Gateway client APIs, third-party Gateway integrationsarea/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/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" 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