@kapa.ai I am trying to sync data from SQLServer to BigQuery. I am facing below rerro for a stable migration io.airbyte.cdk.integrations.source.relationaldb.state.FailedRecordIteratorException: java.lang.RuntimeException: java.lang.NumberFormatException: For input string: "null"

I'm sorry, but the knowledge sources do not contain enough information to directly address the specific error you're seeing:

FailedRecordIteratorException: java.lang.RuntimeException: java.lang.NumberFormatException: For input string: "null"

However, based on the related knowledge sources, here is what I can share: What This Error Likely Indicates The

FailedRecordIteratorException

is a wrapper exception thrown by the

SourceStateIterator

when the underlying record iterator throws an exception during a sync. [SourceStateIterator] The inner

NumberFormatException: For input string: "null"

suggests that somewhere in the sync pipeline, a value that is literally the string

"null"

is being parsed as a number, which fails. Possible Related Issue: v2 → v3 Migration (source-mssql) There is a known bug in source-mssql related to migrations from v2 to v3 (bulk CDK), where: • v2 persisted a

cursor_based

state for empty tables with a null cursor value • After upgrading to v3, if rows were inserted into a previously-empty table, the sync sees the

cursor_field

populated but the cursor value as

null

• Attempting to use

null

as a lower bound for a cursor read causes failures A fix was merged (PR #79128) that makes the connector fall back to a cold start when the cursor value from state is null. [source-mssql fix] Recommendations 1. Check your source-mssql connector version — if you recently upgraded from v2 to v3, the null cursor issue above may be contributing. Upgrading to the latest version that includes the fix from PR #79128 may help. 2. Check for null values in cursor/numeric columns — the

NumberFormatException: For input string: "null"

suggests a field expected to be numeric is receiving the string

"null"

instead of a proper SQL

NULL

. Review your source table for any columns used as cursor fields that might contain null values. 3. Open a support ticket or GitHub issue — since this exact error isn't covered in the available knowledge sources, I'd recommend: ◦ Joining the Airbyte Community Slack ◦ Opening a GitHub issue with your connector versions, sync mode, and full logs Could you share more details such as your source-mssql connector version, sync mode (e.g., cursor-based incremental), and the cursor field type? That would help narrow down the root cause. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.