Populate dlq stage in ParsedConnectionInfo for parseOnly start stream requests

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Atlas Streams
    • Fully Compatible
    • ALL
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      the streams agent expects the stage to be "dlq" for parseOnly requests, and eventually propagates that metadata into the billing events generator and our data warehouse events. omitting the stage is resulting in the dlq ids not being properly set

            Assignee:
            Matthew Normyle
            Reporter:
            Daniel Gil
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: