[ https://issues.apache.org/jira/browse/NIFI-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17360194#comment-17360194 ]
Matt Burgess commented on NIFI-7111: ------------------------------------ I looked into this (and posted my working branch NIFI-7111 under my fork of nifi) and talked to others but I don't think a custom UI makes sense here. The JoltTransformJSON UI doesn't use the actual processor to do the transformation, it gets the spec from the processor's properties and applies it to the input by calling the Jolt library directly. It doesn't do any parsing of the JSON, and indeed it only accepts JSON input. JoltTransformRecord would need a RecordReader instantiated from all the same properties as the reader specified in the processor, meaning it would have to bring in all the record implementations and such just to emulate the same behavior. Also if we limited the test input to JSON it's a disservice to all the other viable input formats such as Avro, XML, etc. I feel like the limitations would make it more confusing than useful. Instead I think we should consider a generic "Test" button on all supporting components where the real component would be called to perform whatever test functionality is appropriate for that component. For JoltTransformRecord that could be a UI with the desired capabilities that calls the real processor on the test input. For DBCPConnectionPool it could test the connection, for an AvroReader it could perhaps show the schema, number of records, etc. > JoltTransformRecord should have an Advanced UI like JoltTransformJSON > --------------------------------------------------------------------- > > Key: NIFI-7111 > URL: https://issues.apache.org/jira/browse/NIFI-7111 > Project: Apache NiFi > Issue Type: Improvement > Reporter: Chris Sampson > Priority: Minor > > For ease, the JoltTransformRecord processor would benefit from having the > same Advanced UI as the JoltTransformJSON processor - i.e. allowing users to > specify and test a JOLT specification against example JSON (Records) from > within the processor. > Presently, one has to either do this in a JoltTransformJSON processor that is > subsequently deleted from the canvas, or find a similar tool external from > NiFi to achieve the task. -- This message was sent by Atlassian Jira (v8.3.4#803005)