-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Atlas Streams
When watch is called with a $source.config.pipeline, we can get back lots of different errors from the target server (if the pipeline fails to parse, the agg layer on the target server might return lots of different error codes).
For the first start of a stream processor, we should report such errors as a user error.