Leland Whitlock
04/27/2026, 6:18 PMkapa.ai
04/27/2026, 6:18 PMjava.lang.IllegalArgumentException: invalid number value null in source-mssql v4.3.6.
However, the knowledge sources do document several known bugs introduced in v4.3.6 that were fixed in v4.3.7, which may be relevant context:
1. TABLESAMPLE on views: Cursor-incremental syncs from SQL Server views fail with a TABLESAMPLE clause can only be used with local tables error. [TABLESAMPLE fix PR]
2. HIDDEN columns on temporal tables: Sampling queries fail with Invalid column name on system-versioned temporal tables with hidden period columns. [HIDDEN columns fix PR]
3. Malformed connector spec: The spec incorrectly listed additionalProperties as a required field, causing strict JSON-schema validators to reject configs. [spec fix PR]
4. check_privileges filtering bypass: Columns with DENY SELECT were not filtered during discovery. [privileges fix PR] Regarding downgrading The knowledge sources do not explicitly discuss the risks of downgrading from v4.3.6 to an earlier version for your specific error. Based on the documented fixes above, upgrading to v4.3.7 (rather than downgrading) appears to be the recommended path, as it addresses multiple regressions introduced in v4.3.6.
I'd recommend:
⢠Upgrading to v4.3.7 if available, as it contains fixes for known v4.3.6 regressions.
⢠If you must downgrade, note that v4.3.5 is referenced as a stable baseline in the knowledge sources (e.g., the temporal table fix mentions "pinning to v4.3.5" as a prior workaround).
For your specific error (invalid number value null), I'd suggest checking the Airbyte GitHub issues or contacting Airbyte support, as this exact error is not covered in the available knowledge sources. š 0 button š 0 button ā¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.kapa.ai
04/27/2026, 6:18 PMjava.lang.IllegalArgumentException: invalid number value null error in source-mssql v4.3.6.
However, the knowledge sources do document several other regressions introduced in v4.3.6 that were fixed in v4.3.7:
⢠TABLESAMPLE on views: Cursor-incremental syncs from SQL Server views fail with The TABLESAMPLE clause can only be used with local tables. [fix PR #76882]
⢠HIDDEN columns on temporal tables: Sampling SQL fails on system-versioned temporal tables with HIDDEN period columns, producing Invalid column name errors. [fix PR #76857]
⢠Malformed connector spec: The published spec incorrectly listed additionalProperties as a required field, causing strict JSON-schema validators to reject configs. [fix PR #76944] Regarding downgrading Based on the knowledge sources, downgrading from v4.3.6 is described as safe and reversible for the fixes listed above. All related PRs explicitly state:
> Can this PR be safely reverted and rolled back? YES [fix PR #76882; fix PR #76857]
However, keep in mind that downgrading to v4.3.5 would mean losing the CDC cold-start fix introduced in v4.3.6 (which fixed the Could not find existing redo log information error for database names with special characters). [fix PR #76384] Recommendation Rather than downgrading, the knowledge sources suggest upgrading to v4.3.7, which contains fixes for the known v4.3.6 regressions. As for your specific invalid number value null error, the knowledge sources do not contain enough information to confirm its cause or whether it is addressed in v4.3.7. I'd recommend checking the Airbyte GitHub issues or contacting Airbyte support for more targeted help. š 0 button š 0 button ā¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.