Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-93627

Add handling for watch() errors when user sets pipeline

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 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.

            Assignee:
            Unassigned Unassigned
            Reporter:
            matthew.normyle@mongodb.com Matthew Normyle
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: