nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre Villard <>
Subject Testing processor from UI
Date Fri, 29 Apr 2016 08:26:31 GMT
Hi team,

Matt has just proposed a great tool helping users in testing scripts into
ExecuteScript processor. And I thought that allowing users to test
processors directly from the UI would be great and save time (when creating
a flow I personally spend time to route my flow files into various
processors to check that I configured the processor correctly to do the
job, or to test some failure cases).

What do you think about the following proposition:

On UI side, there would be a "Testing" tab (see picture, credits Paint),
allowing user (if the processor accepts inputs) to manually enter
attributes (a little bit like ambari with configuration properties : one by
one or in batch mode) and content (with a textarea input like in the
Comments tab), and a button "Test" (enabled only if required processor
properties are set).

When clicking on the button "Test" it would kind of execute the onTrigger
method of the processor and would (for example) open a pop-up with the
generated flow file(s) (the pop-up could have one tab by outgoing
relationship to display attributes/content of every flow file). I think the
best would probably be to execute the method without generating provenance
events, and the generated flow file(s) would be auto-terminated (not really
sent to outgoing relationships).

Obviously, I don't know well enough the whole framework to foresee all the
changes/complications it could introduce. I guess that we would need to
update the ProcessSession to change the behavior in case of a "test

What do you think? Does it sound like something interesting?

Note: on UI side, I wouldn't be able to help much (as you can judge by
yourself with my Paint skills) but if needed I could help on server side.


  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message