fix(connectors): replace overloaded InvalidRecord with distinct error variants

[atharvalade]

Which issue does this PR close?

Closes #3176

Rationale

Error::InvalidRecord was used for five unrelated failure modes in the Iceberg sink's write_data function, making it impossible for callers to distinguish schema mismatches from I/O failures from catalog outages.

What changed?

The Iceberg sink mapped Arrow schema conversion errors, Parquet write failures, and Iceberg catalog transaction failures all to Error::InvalidRecord. Callers could not programmatically decide whether to fix a table definition, skip a corrupt message, or retry a catalog outage.

Three new SDK error variants — SchemaMismatch(String), WriteFailure(String), CatalogError(String) — replace the overloaded InvalidRecord at the appropriate call sites. InvalidRecord is preserved only for the genuine record-batch deserialization error.

Local Execution

• Passed
• Pre-commit hooks ran

AI Usage

• Opu 4.6
• Writing comments, writing PR Description
• Yes

[codecov]

Codecov Report

❌ Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 56.53%. Comparing base (1ae123f) to head (e963fe4).

Files with missing lines	Patch %	Lines
...re/connectors/sinks/iceberg_sink/src/router/mod.rs	0.00%	5 Missing ⚠️

Additional details and impacted files

@@              Coverage Diff              @@
##             master    #3194       +/-   ##
=============================================
- Coverage     73.78%   56.53%   -17.25%     
  Complexity      943      943               
=============================================
  Files          1200     1199        -1     
  Lines        109094    96879    -12215     
  Branches      85994    73779    -12215     
=============================================
- Hits          80492    54770    -25722     
- Misses        25866    39520    +13654     
+ Partials       2736     2589      -147     

Components	Coverage Δ
Rust Core	52.16% <0.00%> (-22.75%)	⬇️
Java SDK	58.44% <ø> (ø)
C# SDK	69.47% <ø> (ø)
Python SDK	81.43% <ø> (ø)
Node SDK	91.44% <ø> (ø)
Go SDK	39.80% <ø> (ø)

Files with missing lines	Coverage Δ
core/connectors/sdk/src/lib.rs	56.17% <ø> (ø)
...re/connectors/sinks/iceberg_sink/src/router/mod.rs	39.23% <0.00%> (ø)

... and 272 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hubcio]

doc "callers may retry on transient catalog outages" is misleading. action.apply() at router/mod.rs:213 is in-memory transaction prep - deterministic failures (invalid partition spec, schema validation) cannot be retried. only tx.commit(catalog) at router/mod.rs:222 hits the network. suggest dropping the retry claim, or splitting into ApplyError (deterministic) vs CommitError (transient-eligible).

[atharvalade]

split CatalogError into TransactionApplyError and CatalogCommitError

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs.

If you need a review, please ensure CI is green and the PR is rebased on the latest master. Don't hesitate to ping the maintainers - either @core on Discord or by mentioning them directly here on the PR.

Thank you for your contribution!

[hubcio]

/author

[atharvalade]

/ready