Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hi All, I Observed That When I Get A Dataset With

Hi all, I observed that when I get a dataset with Dataset.get() , clearml >= 1.6.3 doesn’t allow YYYY-MM-DD format for the version argument anymore, instead I get the following error: clearml.utilities.version.InvalidVersion: Invalid version: '2022-09-07' - could this be a bug?

  
  
Posted 2 years ago
Votes Newest

Answers 11


Is there any documentation on versioning for Datasets? I’ve looked for it but couldn’t find anything.

  
  
Posted 2 years ago

Is there any documentation on versioning for Datasets?

You mean how to select the version name ?

  
  
Posted 2 years ago

Thanks a lot for the clarification!!

  
  
Posted 2 years ago

Sure, I can open a Github issue for it. Thanks for the quick response!

  
  
Posted 2 years ago

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

  
  
Posted 2 years ago

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

  
  
Posted 2 years ago

I think you are correct 😞 Let me make sure we add that (docstring and documentation)

  
  
Posted 2 years ago

Thanks!!

  
  
Posted 2 years ago

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.

  
  
Posted 2 years ago

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! 😁

  
  
Posted 2 years ago

Yes

  
  
Posted 2 years ago