Skip to content
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

[WIP] Remove validate_dataset and regenerate_dataset #373

Merged
merged 4 commits into from
Jul 25, 2024

Conversation

rjzamora
Copy link
Contributor

Closes #372

The validate_dataset and regenerate_dataset are very useful in theory. However, they depend on a lot of fragile machinery that uses in both dask and pyarrow in an "advanced" way. I do not believe the benefits outweigh the maintenance costs.

@rjzamora rjzamora added the breaking Breaking change label Jul 19, 2024
@rjzamora rjzamora self-assigned this Jul 19, 2024
Copy link

Documentation preview

https://nvidia-merlin.github.io/core/review/pr-373

@jperez999 jperez999 marked this pull request as ready for review July 25, 2024 17:36
@jperez999 jperez999 merged commit 6a177d8 into NVIDIA-Merlin:main Jul 25, 2024
17 checks passed
@rjzamora rjzamora deleted the remove-fragile-dataset-utils branch July 26, 2024 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Deprecate validate_dataset and regenerate_dataset
2 participants