[yan-3005]

Describe your changes:

Backport of #36443 to 2.0.

On 2.0, importing a CSV with a malformed quoted field (a stray character after a closing quote, or a quote that is never closed) fails with a server error: Commons CSV 1.12 (same version as main) wraps the lexer error in UncheckedIOException, which both EntityCsv.parse overloads let escape. Sync imports return HTTP 500 and importAsync jobs end FAILED with the raw CSVException text.

This backport:

• catches UncheckedIOException in both parse overloads and reports it as PARSER_FAILURE, so the import returns ABORTED;
• returns null from parse(csv, true) on a parser failure, so recursive database / schema / service / drive-service imports hit the existing records == null guard in importCsv(records, ...) instead of records.get(0) on an empty list;
• words the abort reason as the line and the fix (CsvParseErrorMessage), e.g. line 2 has characters after the closing quote of a quoted value. ... and line 3 starts a quoted value that is never closed. ..., and fixes the "CSV filed" typo.

Conflict resolved: 2.0 does not have restoreFormulas (#36070 is not on 2.0), so only the new documentParserFailure helper was taken from that hunk. On 2.0, parse(csv) still uses .stream().toList(), which raises the same UncheckedIOException.

Blast radius: only malformed CSVs behave differently. The four 2.0 callers of parse(csv, recursive) all pass the result to importCsv(records, ...), which already returns early on null.

Type of change:

• Bug fix

Tests:

Unit tests

• Cherry-picked with the fix.
• On 2.0 + this backport: EntityCsvTest (68), CsvParseErrorMessageTest (3), CsvParseTest (3), CsvUtilTest (10): 84 run, 0 failures.
• Same tests against the original 2.0 EntityCsv.java: test_importMalformedCsvAbortsWithParserFailure and test_recursiveImportOfMalformedCsvAbortsWithParserFailure error with the escaped exception, so the bug is present on 2.0.

Live server evidence (from #36443 on main; same code path and Commons CSV version)

UI screen recording:

Not applicable — backend-only change.

[github-actions]

❌ PR checklist incomplete

This PR cannot be merged until the following are addressed on its linked issue:

• No GitHub issue is linked. Link an issue in the Development section of the PR (or add Fixes #12345 to the description). For a same-org cross-repo issue, add Fixes open-metadata/<repo>#123 to the description.

The fields live on the linked issue in the Shipping project (open the issue → right sidebar → Projects). After you set them, re-run this check (or push a commit) — issue/project changes do not re-trigger it automatically.

Maintainers can bypass this check by adding the skip-pr-checks label.

[gitar-bot]

Code Review ✅ Approved

🟡 Medium risk · Catching unchecked CSV lexer errors routes malformed imports to ABORTED instead of server errors, so those imports may be rejected without importing records.

Backports the CSV import fix so malformed quoted fields abort with a clear parser failure instead of an HTTP 500 or a FAILED async job. Both parse overloads now catch UncheckedIOException and return PARSER_FAILURE, and recursive imports exit cleanly on a null result. No issues found.

Verification

Rules No rules evaluated

Functional validation Not enabled

Set up

Auto-approval Not enabled

Set up

_{For more verification details, comment gitar display:verbose.}

Options

Display: compact → Showing compact verification results.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Powered by Gitar — free for open source}