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
Hello Everyone, I'M Curious To Know If It'S Possible To Prevent Uploading A Duplicate Endpoint. For Instance, If An Endpoint Has Already Been Uploaded Using The

Hello everyone, I'm curious to know if it's possible to prevent uploading a duplicate endpoint. For instance, if an endpoint has already been uploaded using the clearml-serving model add command, and we attempt to upload it again without any changes to the command content, files, or any other aspect, could the system prevent the duplicate upload? It's not crucial, but I'm interested in whether we have a feature like this.

  
  
Posted 8 months ago
Votes Newest

Answers 3


Hi @<1657918706052763648:profile|SillyRobin38>

I'm curious to know if it's possible to prevent uploading a duplicate endpoint.
...and we attempt to upload it again without any changes to the command content,

Basically you overwrite it, and yes, possible 🙂

any other aspect, could the system prevent the duplicate upload?

so basically check the hash and say, no need to upload?

  
  
Posted 8 months ago

so basically check the hash and say, no need to upload?

Thanks for answering, Yes, this is exactly what I wanted

  
  
Posted 8 months ago

Thanks for answering, Yes, this is exactly what I wanted

Hmm should be possible, how slow is the update that we want to save the time ?

  
  
Posted 8 months ago
898 Views
3 Answers
8 months ago
8 months ago
Tags