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
Unanswered
Hi Everyone. I Have A Strange Problem With Pipelines: When I Start A Pipeline To Run In A Queue The Pipeline Is Stuck At The First Pipeline Component. That Is, The Pipeline Itself Is Started And Run (By The Worker Who Observes The Queue) Until The Point W


Hi @<1523701070390366208:profile|CostlyOstrich36> , sorry for my late reply.

My description was not clear enough, what I mean is:

  1. I run a pipeline with run_locally() . This can be any pipeline e.g. the example pipelines like this one None . The pipeline completes.
  2. Then I open the successfully run pipeline in the UI and rerun it in a queue. The queue is observed by agents running in docker mode.
  3. The overall pipeline is "taken out" of the queue and shown as running on the worker. BUT then the pipeline execution does not proceed. I see the first pipeline component (that is the first single step) being enqueued as the next experiment to come but it is never dequeued and never started.
  
  
Posted 11 months ago
117 Views
0 Answers
11 months ago
11 months ago