[ 
https://issues.apache.org/jira/browse/NIFI-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832339#comment-15832339
 ] 

Andrew Lim commented on NIFI-1796:
----------------------------------

This doesn't help solve the core issue of this ticket, but related to the 
documentation comments, I filed 
https://issues.apache.org/jira/browse/NIFI-3345.  Basically, since the 
processor list is so long now, we could make the left nav sections of the doc 
collapsible so areas like the Developer Guide are no longer obscured.

> Create the 'Hello World' example of custom processor development
> ----------------------------------------------------------------
>
>                 Key: NIFI-1796
>                 URL: https://issues.apache.org/jira/browse/NIFI-1796
>             Project: Apache NiFi
>          Issue Type: Task
>          Components: Documentation & Website
>            Reporter: Joseph Witt
>            Assignee: Oleg Zhurakousky
>
> We really need to create a simple guide for how to build custom processor in 
> nifi.  The sort of 'hello world' example.
> This was created due to finding it hard to give a nice simple short pointer 
> for a question on the mailing list.
> We do have a solid developer guide here [1] that goes into the key concepts 
> and processor development a bit.  The next best thing is to use the supplied 
> maven archetype to lay down the fundamental pieces.  You can read a bit more 
> about that here [2].  Finally something that is also quite helpful is looking 
> at the standard processors to see if anything follows the pattern/problem you 
> had in mind and which can serve as a good basis [3]
> [1] https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html
> [2] 
> https://richardstechnotes.wordpress.com/2015/12/06/setting-up-for-custom-nifi-processor-development/
> [3] 
> https://github.com/apache/nifi/tree/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to