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
I'M Trying To Understand The Difference Between Tasks And Pipelines. I Get The Big Picture But The Thing I Struggle To Understand Is The Interplay In The Code Itself. If You Set Up A Pipeline You Wouldn'T Include A Task Init? Or Is There A Reason To Use B

I'm trying to understand the difference between tasks and pipelines. I get the big picture but the thing I struggle to understand is the interplay in the code itself. If you set up a pipeline you wouldn't include a task init? Or is there a reason to use both tasks and a pipeline decorator?

Posted 10 months ago
Votes Newest

Answers 4

Thanks, that's exactly what I was looking for.

Posted 10 months ago

I suggest you take a look at the examples here and play with them a bit 🙂

Posted 10 months ago

Thanks for your reply @<1523701070390366208:profile|CostlyOstrich36> Is there an example where a pipeline is built from existing tasks? I'd like to experiment with it and I don' t see any examples of what you describe with my (clearly lacking) google-fu. What happens if you wrap a function with a task.init() with a pipeline decorator or is that the process you're speaking of?

Posted 10 months ago

Hi @<1545216070686609408:profile|EnthusiasticCow4> , generally speaking, pipelines are a special type of task. When you write steps using decorators you don't have to add the task init. However you can also build pipelines using existing tasks in the system, where those were created with task.init

Posted 10 months ago
4 Answers
10 months ago
10 months ago