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 Trying To Leverage

Hi everyone

Trying to leverage https://clear.ml/docs/latest/docs/pipelines/pipelines_sdk_tasks/#parameter_override in clearml pipelines. I can see that it kinda fails silently - if parameter override causes fail then it rolls back to the value used upon task creation ("default value"), in a task-based pipeline:

`Failed parsing task parameter MyParam=999 keeping default MyParam=['111']

Is there a way to make it throw an error instead of proceeding with default value?

  
  
Posted one year ago
Votes Newest

Answers 2


exact scenario:

i have a task_1, which runs successfully with MyParam=['111'] i have a pipeline controller which runs successfully with task_1 as a step_1
If i use parameter_override for step_1 with value MyParam=999 (yes, not a dict), and run the pipeline, it fails (outputs this error in console logs), then reuses the ['111'] value and completes successfully. And i want it to fail completely, not reuse the safe default historic value

hope it clarifies

  
  
Posted one year ago

Hi GloriousPenguin2 , can you please elaborate more on the exact scenario and add the full error? Is it coming from the controller?

  
  
Posted one year ago
628 Views
2 Answers
one year ago
one year ago
Tags