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. I Will Try Again Since I Got No Answers Previously

Hi. I will try again since I got no answers previously 😁

Posted one year ago
Votes Newest

Answers 5

Alright. I will keep it in mind. Thank you for the confirmation 🙂

Posted one year ago

SuccessfulKoala55 So this is the intended behavior? To always have to select the queue from "Advanced configuration" on the pipeline run window even though the "set_default_execution_queue" is set to the "default" queue?

Besides the fact that tasks will always have "k8s_scheduler" as the queue in the info tab so looking back at a task you will not be able to tell to which queue it was assigned.

Posted one year ago

That's interesting, I don't know enough to answer though. :/ AnxiousSeal95 do you happen to know if this is expected behavior? Or how to have the desired outcome?

Posted one year ago

DangerousDragonfly8 that's correct 🙂

Posted one year ago

Yeah, I get that completely. This is the intended behaviour for k8s glue, but I can see how it creates problems when using pipelines. I'll try to think of a solution that will make it seamless for the user 🙂

Posted one year ago
5 Answers
one year ago
one year ago