Re: Scripted controllers

Sumo et al, I thought about scripted Controller Services when I added NIFI-1458 for scripting reporting tasks. The thing I ran into was that Processors and Reporting Tasks are technically "consumers", at least in the sense that no other NiFi "object" knows about their interfaces, innards, etc.

Re: Scripted controllers

Was planing to upgrade my websocket processor/controller to 0.5.1. Just checking, so that I don't have to build if controller scripting is in roadmap, Nothing important Thanks Sumo > On Feb 20, 2016, at 10:40 AM, Joe Witt wrote: > > Hello Sumo > >

Re: Accessing the name of a Processor programatically

I think Aldrin's points about being able to use properties for the UI are pretty cool, but I also think there's room for the inverse (which is what I think the OP meant). The name of the processor is tied to its instance (though not guaranteed unique between instances, and definitely not unique

[GitHub] nifi pull request: NIFI-1542 PutS3Object Processor Logs Errors Wit...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/240 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi pull request: NIFI-1542 PutS3Object Processor Logs Errors Wit...

Github user trkurc commented on the pull request: https://github.com/apache/nifi/pull/240#issuecomment-186926703 Will start reviewing --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

Re: [DISCUSS] NiFi 0.5.1 release

1536 will be in shortly Sent from my iPhone > On Feb 21, 2016, at 14:17, Joe Witt wrote: > > Tony, > > Just chatted with Oleg. Sounds like he has a potential solution for > NIFI-1536. I did some testing for NIFI-1527 that I've reopened so we > can validate what was

Re: [DISCUSS] NiFi 0.5.1 release

I hope to have a patch for NIFI-1542 this afternoon, unless I run into problems. On Sun, Feb 21, 2016 at 2:17 PM, Joe Witt wrote: > Tony, > > Just chatted with Oleg. Sounds like he has a potential solution for > NIFI-1536. I did some testing for NIFI-1527 that I've

Re: [DISCUSS] NiFi 0.5.1 release

Tony, Just chatted with Oleg. Sounds like he has a potential solution for NIFI-1536. I did some testing for NIFI-1527 that I've reopened so we can validate what was observed. NIFI-1542 is open. NIFI-1536 and NIFI-1542 could be moved off of 0.5.1 but NIFI-1527 should not be. So looks like

[GitHub] nifi pull request: Nifi 1540 - AWS Kinesis Get and Put Processors

GitHub user mans2singh opened a pull request: https://github.com/apache/nifi/pull/239 Nifi 1540 - AWS Kinesis Get and Put Processors Hi: I have implemented kinesis consumer and producer. I've created a new base class for aws processors which do not depend on aws client directly.

Re: Accessing the name of a Processor programatically

Richard, I don't believe the processor name (as you see in the UI or through the REST API) is made available to the processor instance itself at this time. There is no strong/obvious case I can think of quickly to restrict access to the logical name of a ConfigurableComponent like this. Other

Accessing the name of a Processor programatically

Hi, I’ve a use case where each instance of a custom Processor on my flow represents a different instance of a remote system. The message produced by my Processor needs to include the remote system name, and currently I’m using a PropertyDescriptor to allow this to be configured. This means