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 Everyone, I Noticed A Weird Issue With Pipeline Tasks. I Have A Task In My Project With Configuration That Includes Several Parameters Of Different Types (Strings, Ints, Bools). As Soon As I Use This Task To Create A Pipeline Task Using

Hi everyone,
I noticed a weird issue with pipeline tasks. I have a task in my project with configuration that includes several parameters of different types (strings, ints, bools). As soon as I use this task to create a pipeline task using add_step and run the pipeline, all parameters of that task become strings, which is obviously a problem. Is there a particular reason for this that I am missing or is that a bug?

  
  
Posted one month ago
Votes Newest

Answers 6


Hi, it's 1.15.1

  
  
Posted one month ago

to clarify, the parameters are typed correctly inside the pipeline task process itself but logged as strings so they need to be cast manually if I am forwarding some parameters using get_parameter

  
  
Posted one month ago

Just found None which mentions the same issues in HPO

  
  
Posted one month ago

Hi @<1547028074090991616:profile|ShaggySwan64> , which ClearML SDK version are you using?

  
  
Posted one month ago

Hi, version v1.16.1 was just released, can you try it?

  
  
Posted one month ago

Just checked that my older pipeline tasks all had this issue, the oldest one being run on 1.13.2

  
  
Posted one month ago
163 Views
6 Answers
one month ago
one month ago
Tags