Unexpected JSON Path behaviour with NiFi Expression Language in UpdateAttribute (and confusing ReplaceText output)

2020-03-06 Thread Chris Sampson
Hi, (Copied form Slack channel) I’m seeing some confusing behaviours with the Expression Language json path functions and ReplaceText for adding JSON into a file (1.11.3): given input of (read into a FlowFile attribute named record_json via the EvaluateJsonPath processor): { "person": { "

Re: Unexpected JSON Path behaviour with NiFi Expression Language in UpdateAttribute (and confusing ReplaceText output)

2020-03-06 Thread Chris Sampson
A little further investigation/tinkering: I suspect the ReplaceText issue is that the JSON is being parsed and the duplicate metadata field is causing a problem, then one of them is being thrown away adding a teplaceFirst function call the remove the ,"metadata":{} from the attribute first has