Using dataset version uuid for hash calculation in QueryStep#1645
Open
Using dataset version uuid for hash calculation in QueryStep#1645
Conversation
Deploying datachain with
|
| Latest commit: |
eb73958
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f8bb650a.datachain-2g6.pages.dev |
| Branch Preview URL: | https://ilongin-1642-fix-read-datase.datachain-2g6.pages.dev |
shcheklein
reviewed
Mar 13, 2026
| project=None, | ||
| ) | ||
|
|
||
| hash1 = QueryStep(None, ds, "1.0.0").hash() |
Contributor
There was a problem hiding this comment.
how does it work with the QuerySteps like Join, Subtract, etc?
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Before we were using dataset name + version which is not stable between runs because someone could remove version and create new one.