dvc-data is DVC's core data management subsystem, providing functionalities for hashing, indexing, caching, and interacting with various storage backends. As a foundational library for DVC, it receives frequent patch and minor releases to enhance performance, expand compatibility, and fix bugs.
pip install dvc-dataVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates the core functionality of `dvc-data` by creating a `DataIndex` and a `DataIndexEntry` for a local file, simulating how DVC tracks data. It uses `dvc_data.hashfile.hash.file_md5` to calculate the MD5 hash and stores it within the index entry.
Run `dvc cache migrate` to move existing DVC 2.x cache data to the 3.x format. Manually remove deprecated keys from `.dvc` files or regenerate them using `dvc add` if issues persist. Ensure consistent line endings in text files across platforms.
Upgrade to `dvc-data` version 3.18.3 or newer to benefit from fixes for `bulk_exists` behavior across various filesystems and scenarios.
Upgrade to `dvc-data` version 3.18.3 or newer to ensure correct `protocol` propagation in metadata operations.
Increase the operating system's open file descriptor limit (`ulimit -n` on UNIX-like systems) or use a lower value for the `--jobs` parameter.
Ensure all DVC-tracked data is pushed to the remote by running `dvc push`. If the local cache is suspected to be incomplete or corrupted, run `dvc pull` to re-synchronize from the remote. For S3 remotes, you can enable checksum verification with `dvc remote modify <remote_name> verify true` to detect data integrity issues.
Verify that all file paths specified in your .dvc files and DVC configuration are correct and accessible. Check your `dvc config cache.dir` setting. If using symbolic links or hard links, ensure your file system supports them; otherwise, configure `dvc config cache.type copy`. On Windows, enable long path support if dealing with deep directory structures to prevent path limit issues.
Activate your Python virtual environment (if applicable). Reinstall DVC and ensure all necessary dependencies are installed by running `pip install dvc --upgrade` or `pip install dvc[<remote_type>] --upgrade` for specific remote storage support. If 'public' is specifically missing, try `pip install public`.
Double-check the Git repository URL and the exact path to the DVC-tracked data (.dvc file or dvc.yaml output) within that repository. Ensure your Git client is correctly configured with necessary credentials (e.e.g., SSH keys or token) to access the remote repository. Confirm that the source DVC repository has a `dvc remote default` configured for its cache, and that the data is tracked directly (not as an external output via `--external`).