Kaustav Ghosh
10/25/2024, 10:50 AMjava.lang.NullPointerException: Cannot invoke "io.airbyte.protocol.models.AirbyteGlobalState.getStreamStates()" because the return value of "io.airbyte.protocol.models.AirbyteStateMessage.getGlobal()" is null
at io.airbyte.workers.internal.bookkeeping.ParallelStreamStatsTracker.updateDestinationStateStats(ParallelStreamStatsTracker.kt:130) ~[io.airbyte-airbyte-commons-worker-1.1.0.jar:?]
at io.airbyte.workers.internal.syncpersistence.SyncPersistenceImpl.updateDestinationStateStats(SyncPersistence.kt:322) ~[io.airbyte-airbyte-commons-worker-1.1.0.jar:?]
at io.airbyte.workers.internal.bookkeeping.AirbyteMessageTracker.acceptFromDestination(AirbyteMessageTracker.kt:65) ~[io.airbyte-airbyte-commons-worker-1.1.0.jar:?]
at io.airbyte.workers.general.ReplicationWorkerHelper.internalProcessMessageFromDestination(ReplicationWorkerHelper.kt:443) ~[io.airbyte-airbyte-commons-worker-1.1.0.jar:?]
at io.airbyte.workers.general.ReplicationWorkerHelper.processMessageFromDestination(ReplicationWorkerHelper.kt:317) ~[io.airbyte-airbyte-commons-worker-1.1.0.jar:?]
at io.airbyte.workers.general.BufferedReplicationWorker.readFromDestination(BufferedReplicationWorker.java:488) ~[io.airbyte-airbyte-commons-worker-1.1.0.jar:?]
at io.airbyte.workers.general.BufferedReplicationWorker.lambda$runAsync$2(BufferedReplicationWorker.java:215) ~[io.airbyte-airbyte-commons-worker-1.1.0.jar:?]
at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
user
10/25/2024, 10:50 AMAirbyteStateMessage.getGlobal()
method is returning null, which then causes a NullPointerException
when trying to invoke getStreamStates()
on the result. 4. This issue has been observed in different versions of Airbyte, including 0.61.0, 0.64.1, and 1.1.0 (as seen in your stack trace). 5. It appears to be particularly problematic with CDC (Change Data Capture) syncs, but has also been reported in other scenarios. Unfortunately, based on the available information, there doesn't seem to be a clear solution provided for this issue. Some users have reported that the error occurs with specific destinations but works with others. For example, one user mentioned that it works with other destinations but not with DuckDB [destination-duckdb](https://github.com/airbytehq/airbyte/issues/38749). If you're encountering this error, you might try the following: 1. Check if the issue persists with a different destination connector. 2. If you're using CDC, try disabling it to see if that resolves the issue. 3. Ensure you're using the latest version of both Airbyte and the specific connectors you're using. 4. If the problem persists, consider reporting it on the Airbyte GitHub repository with details about your specific setup and use case. Given that this issue has been reported across multiple connectors and versions, it may be a deeper problem within Airbyte's replication process that needs to be addressed by the Airbyte team.