[NIFI-8342] SplitJson corrupting flowfile content

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.13.1
• Fix Version/s: 1.13.2
• Assignee: Unassigned
• Reporter: Dorian Bugeja
• Created: 18/Mar/21 16:38
• Updated: 19/Mar/21 12:25
• Resolved: 18/Mar/21 16:46

Description

When performing a SplitJson on an array of complex json files where the first record has a longer content/text field 

[ {
  "brand_id" : null,
  "table_name" : "xx",
  "attribute" : "x",
  "category" : "x",
  "include" : null,
  "exclude" : null
}, {
  "brand_id" : null,
  "table_name" : "x",
  "attribute" : "x",
  "category" : "x",
  "include" : null,
  "exclude" : null
} ]

an invalid json is generated (content looks file, but subsequent EvaluationJsonPath is unable to parse the object). If first table_name value is set to x, no issue is encountered 

 

Issue Links

• is caused by: NIFI-8337 When reading FlowFile content, processor can start at wrong offset
• is related to: NIFI-8334 EvaluateJsonPath regression in NiFi version 1.13.1