HCK-15381: fix possible JSON parse error

[taras-dubyk]

Content

Fix JSON parse error in filterCorruptedData when Databricks response is truncated mid-table

When reverse engineering large schemas, Databricks may truncate API responses by inserting a *** WARNING: max output size exceeded, skipping output. *** marker in the middle of the output. The filterCorruptedData function attempts to recover valid JSON by discarding incomplete objects from both sides of the split.

Root cause: Two bugs in the isTruncatedInMiddle branch:

• Wrong join delimiter — filtered chunks were joined with ', ' instead of JSON_OBJECTS_DELIMITER (}, {). This consumed the object boundary, merging two table objects into one and causing silent data loss (duplicate keys resolved by last-wins semantics).

• Empty chunk not handled — when the second chunk contains only a single incomplete table (no }, { delimiter), filterCorruptedStart returns an empty string. Joining with ', ' produced a trailing comma ("..., ") which caused JSON.parse to throw: SyntaxError: Expected double-quoted property name in JSON at position ...

Fix:

• Use JSON_OBJECTS_DELIMITER for joining to preserve proper JSON object boundaries
• Filter out empty strings before joining
• Conditionally append }]} only when the last chunk contributed no complete tables

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud