Re: Restricting Controller Service Class Definitions

I had thought about the interface extension, but thought i should probably field the question first. Thanks much for the prompt feedback. I'll go forward with the recommended solution. Thanks! On Mon, Aug 14, 2017 at 12:12 PM Andy LoPresto wrote: > I don’t think this

Re: Restricting Controller Service Class Definitions

I don’t think this extends to the general case, but in this instance, I support Bryan’s first suggestion. The RestrictedSSLContextService interface will extend the SSLContextService interface, and the StandardRestrictedSSLContextService class can implement that interface and extend

Restricting Controller Service Class Definitions

All, I'm in the process of making some changes to a processor which exposes a controller service with several implementations. However, I only want to allow a particular implementation for the processor, but i've not found a clean way to do this. The rationale behind wanting to do this can be

Need help in designing the solution.

Hi, I have a use case where "I am reading bunch of rows from a database table, apply some rules(eg. amount > 100) and add additional columns depending on the rules that got satisfied, and then store the updated rows into elastic search". The approach I have in mind at the moment is : 1. Use

[NiFi-4290] Re: NiFi 1.4: PublishKafkaRecord_0_10: failed to process due to java.lang.NullPointerException

Hello Joe, I have added all the details to NiFi-4290. Please let me know if you need any other information from my side. Thanks Mayank On Sat, Aug 12, 2017 at 12:00 AM, Joe Witt wrote: > Thanks for reporting the issue. It appears the NPE can occur if zero > records end up

Re: how to execute code when processor is stopping

Thanks Koji, this is exactly what I'm looking for. Regards, Ben 2017-08-14 12:21 GMT+08:00 Koji Kawamura : > Hi Ben, > > AbstractSessionFactoryProcessor has a protected isScheduled() method, > that can be used by a processor implementation class to check whether > it is