Altan Sener
03/31/2026, 8:40 PMkapa.ai
03/31/2026, 8:40 PMcom.google.cloud.bigquery.BigQueryException: java.lang.InterruptedException occurring in BigqueryDirectLoadDatabaseInitialStatusGatherer.getTableStatus() — is a known issue with the BigQuery destination connector. Root Cause The BigQuery Java SDK internally calls AbstractFuture.get(), which throws InterruptedException when the thread is interrupted. When this blocking call runs inside a Kotlin coroutine that gets cancelled (e.g., due to a timeout or parent scope cancellation), the SDK wraps the InterruptedException in a BigQueryException. This is then treated as a hard failure instead of a graceful cancellation. [fix PR]
This specific error originates during the setup/initialization phase of the sync, when the connector gathers initial table status via bigquery.getTable(). [fix PR] Status This is a known bug that has been reported approximately 15 times in the last 30 days. A fix has been proposed (PR #75912) that:
1. Introduces a bigQueryCall() suspend helper that runs blocking BigQuery SDK calls on Dispatchers.IO
2. Catches BigQueryException whose cause is InterruptedException and converts it to a CancellationException (graceful cancellation)
3. Restores the thread interrupt flag via Thread.currentThread().interrupt() before rethrowing
[fix PR] What You Can Do Now • Retry the sync — this is typically a transient error caused by the sync being cancelled due to a timeout or upstream failure. It usually resolves on retry. [fix PR]
• Upgrade the connector once the fix in PR #75912 is merged and released, as it will handle this exception gracefully instead of treating it as a hard failure. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.