nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy LoPresto <>
Subject Re: Contributing to Nifi
Date Tue, 26 Mar 2019 15:58:48 GMT
Hi Chris, 

Thanks for getting involved and contributing back to the community. There is no formal voting
process to prioritize contributions — the Contributor Guide [1] and Developer Guide [2]
have a lot of useful information around this. In general, for conversations like the one you’re
asking for, an email to the list is sufficient, and anyone who feels strongly will weigh in
here. Once you’ve had a discussion around this, you can prioritize your contributions, open
Jira tickets for each, and create the pull requests. A committer will need to provide formal
acceptance before the code can be merged, so this may require multiple rounds of comment/discussion/patching.
All committers have a lot of responsibilities, so the expectations around time frame to merge
may be extended right now. But opening the PRs will definitely get some community feedback,
so I encourage you to do that. 

To create/assign Jiras, please reply here with your username (and those of your colleagues
if applicable), and I will give you the proper permissions in our Jira instance. 

Personally I am most interested in the EncryptValue processor, so depending on my tasking
for the next few days, that’s where I would likely focus my attention if available. 

[1] <>
[2] <>

Andy LoPresto
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Mar 26, 2019, at 7:11 AM, Chris Lundeberg <> wrote:
> Hi all,
> I hope this message finds everyone well. My company is starting to build a
> few custom solutions using Nifi, for a few clients.  We want to be more
> involved in the Nifi community and start contributing back some of the work
> we have done. We have a few processors that we have created and pushed to
> open repos, but would like to try and get some of them built into the base
> Nifi distro, if possible.  We are doing a lot of research now to understand
> what that looks like and I think are ready to start picking up and creating
> Jira tickets.  My main question for this thread is with new processors; if
> we have several that we think could be a good addition, is there some kind
> of voting process that might help us understand which ones would actually
> be of value to the greater community or is that just decided on a PR
> basis?  Some of the example processors that we have created / are creating
> are:
> 1. *EncryptValue* - Reads a list of values from an attribute and loops over
> the keys within the data.  As it finds the matches, it will hash the value
> based on the type that the user selects (we support all the normal ones).
> 2. *StandardizeDate* - Reads a key/value pair from an attribute and loops
> over the keys within the incoming data.  If it finds a match, it will
> standardize the value of that key as ISO-8601.
> 3. *AvroBulkInsert* - We utilize the bulk insert functionality within MSSQL
> to insert incoming avro files.
> 4. *GetColumns* - A user selects the controller service and database type
> and we will fetch the columns from the database/schema.table provided and
> attach as a comma separated value on an attribute or flowfile.
> Any advice/suggestions would be greatly appreciated. Thanks!
> Chris Lundeberg
> *Modern Data Engineer / Data Engineering Practice Lead*
> <>
> <>  <>
> <>  <>
> 1904labs is proud to be a Top Workplace 2018
> <>

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