Re: [DISCUSS] Google Summer of Code 2018

Hi Matt, not sure it matches the GSoC. I am thinking about process mining. Take the Provenance/Data Lineage information from the NiFi repository or from Apache Atlas (and maybe some additional information from the processors) and analyze whether the processes are optimal and display it

[DISCUSS] MiNiFi Flow Designer

Hey folks, With the release of Registry, I’ve been contemplating leveraging it and the current codebase of NiFi to facilitate ease of use for MiNiFi flow design. One of the areas I would like to form a concerted effort around is that of the Command and Control (C2) functionality originally

Re: [DISCUSS] Google Summer of Code 2018

Matt Did you have some ideas/features/enhancements in mind you think would be good to propose? Thanks Joe On Tue, Feb 27, 2018 at 6:56 PM, Matt Burgess wrote: > If you haven't heard yet, the Apache Software Foundation was selected > as an organization for this year's

[DISCUSS] Google Summer of Code 2018

If you haven't heard yet, the Apache Software Foundation was selected as an organization for this year's Google Summer of Code [1]. I've seen activity on other Apache projects' mailing lists requesting ideas for issues, features, components, etc. that could be good proposals/ideas for GSoC, and

Re: get access token inside custom processor

Thanks Bryan I got it, I thought the processor would be running as the user that had logged into the NIFI web UI. Regards, Ben 2018-02-27 22:31 GMT+08:00 Bryan Bende : > Hello, > > Your custom processor would be the same as if you were writing an > external client program. > >

Re: Policies for root Process Group.

Daniel, What is your timeframe for needing this working? I ask because the contributors to NiPyApi are very close to a release which will provide by secured environment support, and wrappers to set this kind of policy via a Python Client SDK for NiFi.

Re: PutElasticsearchHttpRecord writing null values

Ok. I'll take a look when I get a chance. On Tue, Feb 27, 2018 at 10:12 AM, Robert R. Bruno wrote: > Added my patch in NIFI-4743 in JIRA. > > Robert > > On Tue, Feb 27, 2018, 06:10 Robert R. Bruno wrote: > > > I use this processor extensively and patches

Re: PutElasticsearchHttpRecord writing null values

Added my patch in NIFI-4743 in JIRA. Robert On Tue, Feb 27, 2018, 06:10 Robert R. Bruno wrote: > I use this processor extensively and patches it to have the option to > supress nulls. I've been meaning to share this back. This way one can set > how to treat nulls just like

Re: Policies for root Process Group.

Making a call to "/process-groups/root" should retrieve the root process group which should then have an id element. On Mon, Feb 26, 2018 at 5:20 PM, Daniel Hernandez wrote: > Thanks Matt, > > I get now what is the problem, in order to exhaust all my

Re: get access token inside custom processor

Hello, Your custom processor would be the same as if you were writing an external client program. You would need to provide the processor with a username and password in the processor properties, and then it would need to make a call to the token REST end-point. Processors don't run as the user

Re: PutElasticsearchHttpRecord writing null values

I use this processor extensively and patches it to have the option to supress nulls. I've been meaning to share this back. This way one can set how to treat nulls just like the jsonrecordsetwriter. Robert On Mon, Feb 26, 2018, 07:31 Mike Thomsen wrote: > I have a