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
Should Dataset Triggers Also Be Activated If There Is No Trigger Condition Except Dataset_Project And A New Task Starts In That Project? Is This Expected Behavior?

Should Dataset Triggers also be activated if there is no trigger condition except dataset_project and a new task starts in that project? Is this expected behavior?

  
  
Posted 2 years ago
Votes Newest

Answers 17


trigger_scheduler.add_dataset_trigger(schedule_task_id=TASK_ID, schedule_queue='default',
trigger_project='Cassava Leaf Disease Classification', name='start task on data - End Game')

  
  
Posted 2 years ago

In this case, it would wait until any change occurred in the project mentioned here. Even if a task started, and not a dataset change or publish or anything, it would trigger.

  
  
Posted 2 years ago

So in my case where I schedule a task every time I publish a data, when I publish my dataset once, it triggers and starts a new task.

  
  
Posted 2 years ago

However, since a new task started in the project, it would again start a new task.

  
  
Posted 2 years ago

Can you please provide a snippet of your implementation?

  
  
Posted 2 years ago

then I use trigger_scheduler.start()

  
  
Posted 2 years ago

recursively.

  
  
Posted 2 years ago

I just assumed it should only be triggered by dataset related things but after a lot of experimenting i realized its also triggered by tasks...

VexedCat68 I think you are correct, and it should only be triggered by "Dataset" Tasks, that said maybe there is a bug , in which case if there are no additional filters it will get triggered on Any change in the project. This will explain how adding the tags filter solved the issue.
wdyt?

  
  
Posted 2 years ago

I just assumed it should only be triggered by dataset related things but after a lot of experimenting i realized its also triggered by tasks, if the only condition passed is dataset_project and no other specific trigger condition like on publish or on tags are added.

  
  
Posted 2 years ago

Nice, that seems to be the issue. Any chance you can open a GitHub issue, so we do not loose track of it ?

  
  
Posted 2 years ago

Agreed. The issue does not occur when I set the trigger_on_publish to True, or when I use tag matching.

  
  
Posted 2 years ago

Let me play with it a bit and see if I can find more 🙂

  
  
Posted 2 years ago

I'm curious as to if this is buggy behavior or if it is expected?

  
  
Posted 2 years ago

I'll do that.

  
  
Posted 2 years ago

main clearml repo?

Yep that sounds right 🙂 thank you!

  
  
Posted 2 years ago

do I just post the issue on the main clearml repo?

  
  
Posted 2 years ago

Done

  
  
Posted 2 years ago
653 Views
17 Answers
2 years ago
one year ago
Tags