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

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Atlas Streams
    • Fully Compatible
    • Sprint 67
    • None
    • 3
    • 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:
              Guy-Jacques Isombe
              Reporter:
              Calvin Nix
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: