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
Question About Using S3 As Artifact Storage - Do We Need To Setup S3 Credentials On Every System That Is Using Those Artifacts (E.G. In Clearml-Agent Where Model Upload Happens, Or In A Prediction Service, That Needs To Download The Latest Model)

question about using s3 as artifact storage - do we need to setup s3 credentials on every system that is using those artifacts (e.g. in clearml-agent where model upload happens, or in a prediction service, that needs to download the latest model)

  
  
Posted 3 years ago
Votes Newest

Answers 5


thanks for info

  
  
Posted 3 years ago

BTW: server-side vault is in progress, hopefully will be available in the upcoming releases :)

  
  
Posted 3 years ago

With pleasure 🙂

  
  
Posted 3 years ago

Hi FiercePenguin76
So currently the idea is you have full control over per user credentials (i.e. stored locally). Agents (depending on how deployed) can have shared credentials (with AWS the easiest is to push to the OS env)

  
  
Posted 3 years ago

or somehow, we can centralize the storage of S3 credentials (i.e. on clearml-server) so that clients can access s3 through the server

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