Processing Connector Output and Handling Control Messages

Summary

The message logs show the processing of connector output, handling control messages, and marking workload as successful.


Question

2024-10-24 15:24:11 INFO i.a.w.l.p.s.m.Stage(apply):39 - APPLY Stage: CLAIM — (workloadId = b117307c-14b6-41aa-9422-947e34922962_ef872cbd-dbe0-462b-b532-be35bb1ba096_0_check) — (dataplaneId = local)
2024-10-24 15:24:19 INFO i.a.c.i.LineGobbler(voidCall):166 -
2024-10-24 15:24:19 INFO i.a.c.ConnectorWatcher(processConnectorOutput):114 - Connector exited, processing output
2024-10-24 15:24:19 INFO i.a.c.ConnectorWatcher(getConnectorOutputStream):151 - Output file jobOutput.json found
2024-10-24 15:24:19 INFO i.a.c.i.LineGobbler(voidCall):166 - ----- START CHECK -----
2024-10-24 15:24:19 INFO i.a.c.i.LineGobbler(voidCall):166 -
2024-10-24 15:24:19 INFO i.a.c.ConnectorWatcher(processConnectorOutput):117 - Connector exited with exit code 0
2024-10-24 15:24:20 INFO i.a.w.i.VersionedAirbyteStreamFactory(create):189 - Reading messages from protocol version 0.2.0
2024-10-24 15:24:20 WARN i.a.m.l.MetricClientFactory(getMetricClient):43 - MetricClient has not been initialized. Must call MetricClientFactory.CreateMetricClient before using MetricClient. Using a dummy client for now. Ignore this if Airbyte is configured to not publish any metrics.
2024-10-24 15:24:20 INFO i.a.w.i.VersionedAirbyteStreamFactory(internalLog):308 - Using concurrent cdk with concurrency level 10
2024-10-24 15:24:20 INFO i.a.w.i.VersionedAirbyteStreamFactory(internalLog):308 - using SANDBOX of Salesforce
2024-10-24 15:24:20 WARN i.a.w.i.VersionedAirbyteStreamFactory(internalLog):305 - The response for <https://test.salesforce.com/services/oauth2/token> was expected to be a list with at least one element but was b'{"error":"invalid_grant","error_description":"expired access/refresh token"}'
2024-10-24 15:24:20 INFO i.a.c.ConnectorMessageProcessor(updateConfigFromControlMessage):231 - Checking for optional control message…
2024-10-24 15:24:20 INFO i.a.c.ConnectorMessageProcessor(updateConfigFromControlMessage):253 - Optional control message not found. Skipping…
2024-10-24 15:24:20 INFO i.a.c.ConnectorWatcher(saveConnectorOutput):162 - Writing output of b117307c-14b6-41aa-9422-947e34922962_ef872cbd-dbe0-462b-b532-be35bb1ba096_0_check to the doc store
2024-10-24 15:24:20 INFO i.a.c.ConnectorWatcher(markWorkloadSuccess):167 - Marking workload b117307c-14b6-41aa-9422-947e34922962_ef872cbd-dbe0-462b-b532-be35bb1ba096_0_check as successful
2024-10-24 15:24:20 INFO i.a.c.ConnectorWatcher(exitProperly):215 - Deliberately exiting process with code 0.
2024-10-24 15:24:20 INFO i.a.c.i.LineGobbler(voidCall):166 -
2024-10-24 15:24:20 INFO i.a.c.i.LineGobbler(voidCall):166 - ----- END CHECK -----
2024-10-24 15:24:20 INFO i.a.c.i.LineGobbler(voidCall):166 -



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["processing-connector-output", "handling-control-messages", "marking-workload-successful", "connector-exit-code"]