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
Why There Is No

Why there is no auto_connect_frameworks argument in Task.create but only in Task.init ?

  
  
Posted 12 months ago
Votes Newest

Answers 3


Hi @<1618056041293942784:profile|GaudySnake67>
Task.create is designed to create an External task not from the current running process.
Task.init is for creating a Task from your current code, and this is why you have all the auto_connect parameters. Does that make sense ?

  
  
Posted 12 months ago

By default the remote link (i..e the Task you are creating with Task.create will have all the auto logging turned on)
For finer control we kind of assume you have Task.init inside your remote script, and then just pass add_task_init_call=False does that make sense ?
Do you think we should have a way to configure those auto_connect args when creating the Task?

  
  
Posted 11 months ago

Sure, but why wouldn't I want the ability to control auto_connect_parameters even in an external task?

  
  
Posted 12 months ago
712 Views
3 Answers
12 months ago
11 months ago
Tags
Similar posts