markap14 commented on PR #7782: URL: https://github.com/apache/nifi/pull/7782#issuecomment-1743139339
@dan-s1 @ChrisSamo632 @r-vandenbos I do think we want to be careful here. Breaking it up into two processors that really do essentially the same thing is probably a mistake in my opinion. I think it makes much more sense to have a single processor and let a property determine whether or not it's expecting multiple JSON documents. We'd also want to avoid any mention of a "JSON Record" - the entire point of Records is that it doesn't matter whether the bytes are in JSON, XML, Logs/plaintext, Avro, etc. They are records. It would definitely make sense to me to take the approach that Chris pointed out - to have two relationships - valid and invalid, where each individual JSON element is routed to one or the other. So each incoming FlowFile would be split into, at most, 2 FlowFiles. This would be consistent with how ValidateRecord works. Jolt is broken into two different processors because JoltTransformJSON was created before NiFi had a notion of records. So then we created JoltTransformRecord in order to allow the same JOLT language to be used for Avro, XML, etc. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
