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
Hi, Quick Y/N Question: Is It Possible To Build A Pipeline Of Pipelines? I'D Imagine This To Be Possible, Since Pipelines Are Also Treated As Tasks.


Quick Y/N question: is it possible to build a pipeline of pipelines? I'd imagine this to be possible, since pipelines are also treated as tasks.

Posted 9 months ago
Votes Newest

Answers 2

Thanks for the answer - just thinking about how to build an easy solution for new feature requests.

Combining pre-existing pipes in the described way would make things "simpler" the way I see it, but could also lead to other problems. Will have to think about it a little more.

Posted 9 months ago

Hi @<1523703572984762368:profile|SlimyDove85> , conceptually I think it's possible. However, what would be the use case? In the end it would all be abstracted to a single pipeline

Posted 9 months ago
2 Answers
9 months ago
9 months ago