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, Just A Silly Question. Using Clearml-Data, Am I Right To Say Every Data Commit Is Immutable, As In , It Isnt Possible To Open An Existing Task-Id(For Datasets), And Modify Them , And Still Save Them To The Same Data Commit Id ?

Hi, Just a silly question. Using clearml-data, Am I right to say every data commit is immutable, as in , it isnt possible to open an existing task-id(for datasets), and modify them , and still save them to the same data commit id ?

  
  
Posted 3 years ago
Votes Newest

Answers 3


That's right. once you call clearml-data close, the completed dataset is immutable. This is a very important feature if traceability is important as once an experiment uses a dataset version, we want to make sure it doesn't change without leaving a trace!

  
  
Posted 3 years ago

DeliciousBluewhale87
You could also just upload the data (i.e do not call close). Then you will be able to change it later obviously, this will make in intractable.
BTW: the clearml-data stores delta changes, so if you only change a few files it will only store those.

  
  
Posted 3 years ago

Thanks guys.. perfect..

  
  
Posted 3 years ago
1K Views
3 Answers
3 years ago
one year ago
Tags