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, When A Step In A Pipeline Is Aborted, It Is Marked As Gracefully Finished (Painted In Blue) And The Other Steps That Depend On It Continue. I Believe This Is Not The Expected Behavior, I'D Expect To To Be Marked As Failed, So Other Tasks That Depend

Hi, when a step in a pipeline is aborted, it is marked as gracefully finished (painted in blue) and the other steps that depend on it continue. I believe this is not the expected behavior, I'd expect to to be marked as failed, so other tasks that depend on it wouldn't be executed. What do you say?
At the moment, If I have to abort a task, I would want to make some changes and re-run the pipeline from where it stopped (right before the task I aborted), and right now the pipeline simply continues 😞

  
  
Posted 3 years ago
Votes Newest

Answers 10


If this could be so, I'd be happy to have this as a feature, this really impacts my pipeline flow.

  
  
Posted 3 years ago

I aborted the task because of a bug on my side

  
  
Posted 3 years ago

But maybe only one step in the dag is flawed and I want to continue the rest of the pipeline as usual (despite the branch of the flawed task).
I am not sure what you mean by automatic stopping flows, could you give an example?

  
  
Posted 3 years ago

I aborted the task because of a bug on my side

🙂

Following this one, is treating abort as failed a must feature for the pipeline (in your case) or is it sort of a bug in your opinion ?

  
  
Posted 3 years ago

For example HPO, early stopping. It would mark the Task as aborted. Make sense ?

  
  
Posted 3 years ago

I think it should be treated as failed, I am truly not convinced as why aborting a task should be anything beside a user terminating an unwanted behavior of the task (be it bug, running with wrong config, task getting stuck etc..)

  
  
Posted 3 years ago

For example HPO, early stopping. It would mark the Task as abortedWhy? The task should have completed successfully, how is this aborting?

  
  
Posted 3 years ago

Why? The task should have completed successfully, how is this aborting?

Early stopping by the HPO process, like hyper-band, e.g. this training model is going nowhere let's stop it.

  
  
Posted 3 years ago

SmarmySeaurchin8 it could be a switch, the problem is that when you have automatic stopping flows, they will abort a task, which is legitimate (e.g. should not considered failed)
How come you have aborted tasks in the pipeline ? If you want to abort the pipeline, you need to first abort the pipeline Task then the tasks themselves.

  
  
Posted 3 years ago

I think it should be treated as failed,

I'm not sure where I stand on default behavior, it it could easily be an argument for the pipeline controller

  
  
Posted 3 years ago
631 Views
10 Answers
3 years ago
one year ago
Tags