James,
I’m wondering if a page outlining a toy processor (something like `CountText`
or `ReverseContent`) and doing a line-by-line annotation from a developer’s
perspective would be helpful. It could be a few sections:
1. How to get to this point
* running the maven archetype
*
9) Oh, and the wiki is a little hard to navigate and the contents rather patchy
On Fri, 25 Jan 2019 at 21:57, James Srinivasan
wrote:
>
> As someone relatively new to NiFi dev, here's my £0.02. (Yes, I
> realise I could and possibly should submit PRs :)
>
> 1) I'm used to Java and Maven, so used
As someone relatively new to NiFi dev, here's my £0.02. (Yes, I
realise I could and possibly should submit PRs :)
1) I'm used to Java and Maven, so used the archetype. It worked fine,
it would have been nice it if set up unit tests for me.
2) The User and Developer documentation is great and
I am not against the archetype. But we need to spell out every step of the
way. I'd like to see a user thinking about their custom logic ASAP rather
than fighting the tools to get started. Those steps should be brain-dead,
just reflexes, if you know what I mean. Hell, let them create a custom
That makes sense about the best practice for deploying to an
additional lib directory.
So for the project structure you are saying it would be easier to have
a repo somewhere with essentially the same thing that is in the
archetype, but they just clone it and rename it themselves (what the
We assume they create new projects from archetypes every day. They don't.
We also assume they know how to deploy new NARs. Most don't. Especially if
we want them to follow best practices and create an additional NAR bundles
directory entry im the config (vs dumping into nifi lib).
I can attest
Andrew,
I'm not disagreeing with your points, but I'm curious how you see
those two ideas being different from the processor archetype and the
wiki page with the archetype commands?
Is it just that people don't know about it?
-Bryan
[1]
I think this ties into my other discuss thread on refreshing the archetypes
On January 25, 2019 at 11:50:10, Andrew Grande (apere...@gmail.com) wrote:
I consistently see my users struggling when they move up the nifi food
chain and start looking at custom processors. The good content about
I should be able to find some time to set up some skeletons based on code
that I've written. Would storing them in the docs folder work, so we can do
PRs?
On Fri, Jan 25, 2019 at 11:50 AM Andrew Grande wrote:
> I consistently see my users struggling when they move up the nifi food
> chain and
I consistently see my users struggling when they move up the nifi food
chain and start looking at custom processors. The good content about
prototyping processsors via scripting processors and finalizing with a full
NAR bundle is everywhere but where it should be.
A few simple changes could help
One of the changes we should make is to create a separate guide for product
vendors on how to build and maintain a bundle. We're at that point where
vendors will have to do it on their own as extension providers, so it would
be very helpful for them to have a simple and straight forward document
I think we have a lot more documentation than most projects, but I
think an issue is that content is scattered in many different
locations, and some of the docs are huge reference guides where it can
be hard to find all the pieces of what you are trying to do.
The first thing a new contributor
12 matches
Mail list logo
