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

Treat most $source.config.pipeline parsing errors as user errors on 'fresh' starts

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Atlas Streams
    • Fully Compatible
    • Sprint 67
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There are a lot of error codes aggregation can throw for parsing errors. For processors that set $source.config.pipeline, we should be able to treat these parsing errors as user errors.

       

      In order to reduce risk, we should only treat these errors as user errors for processors that are starting 'fresh' i.e. not starting from a checkpoint.

       

      context:

      https://github.com/10gen/mongo/pull/31758/files#r1934776008

       

            Assignee:
            guyjacques.isombe@mongodb.com Guy-Jacques Isombe
            Reporter:
            calvin.nix@mongodb.com Calvin Nix
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None