Hi SmallGiraffe94
I think it now has to be a semantic version (like pyhton packages for example)
This is so that the auto version increment can bump to the next one automatically.
Maybe adding the date as a tag would make sense? what do you think?
Or maybe in the description field
SmallGiraffe94 You should use dataset_version=2022-09-07 (not version=... ). This should work for your use-case.Dataset.get shouldn't actually accept a version kwarg, but it does because it accepts some **kwargs used internally. We will make sure to warn the users in case they pass values to **kwargs from now on.
Anyway, this issue still exists, but in another form:Dataset.get can't get datasets with a non-semantic version, unless the version is specified using the dataset_version argument Users can't create new datasets if a dataset with a non-semantic version exists in the project (unless dataset_version is specified) Users can't change the dataset versionWe will make sure to address these issues (hopefully by the next release).
Thank you! 😁
Is there any documentation on versioning for Datasets?
You mean how to select the version name ?
Sure, I can open a Github issue for it. Thanks for the quick response!
I think you are correct 😞 Let me make sure we add that (docstring and documentation)
Hm, one of the issues I have with this change is that now every dataset hat doesn’t have a semantic version cannot be loaded anymore
Okay we definitely need to solve that.
Any chance I can ask to open a github issue (just so we do not forget).
I will pass it quickly along so that we can maybe offer a fix in the next RC
Hm, one of the issues I have with this change is that now every dataset hat doesn’t have a semantic version cannot be loaded anymore - I would have to re-upload every dataset with a reformatted version.
Is there any documentation on versioning for Datasets? I’ve looked for it but couldn’t find anything.