Re: Custom Processor

Hi Oleg, Executesql is not the problem, but I am trying to achive something different here. Exevutesql was just an example. Based on following article, https://dzone.com/articles/apache-nifi-not-from-scratch i was trying to export classes of my existing application onto nifi custom processor.

Re: Custom Processor

Hi, One enhancement I could think of would be to give an options to bring data (in JSON) in FlowFile attribute instead of content. It will be up to the user to ensure that not too much of data is pulled back causing heap issues, and also not hit the database frequently. Regards, Manish On Thu,

Re: Custom Processor

Hi You can obviously extends the executesql processor, but I am more interested in understanding what exactly are you trying to accomplish that executesql doesn’t do today. Don’t get me wrong as I am sure you may have a legitimate reason, but there may also be missing functionality that we may

Custom Processor

Hi Nifi Team, I want to create a custom processor in which I want to use the database functionality. Such as, i want to extract some information from database as part of processor. I could Access the database controller service but how do I reuse executesql processor in my custom processor?

Re: ConsumeJMS and Acknowledgement Mode

Good point about lambda. Let me see if I can refactor it a bit. And sure, please share your patch. Would love to compare. Cheers Oleg > On Sep 15, 2016, at 11:10 AM, McDermott, Chris Kevin (MSDU - > STaTS/StorefrontRemote) wrote: > > Oleg, > > Thanks very much. Yes,

Re: ConsumeJMS and Acknowledgement Mode

Oleg, Thanks very much. Yes, I fully agree with you. I saw your PR and noted that it’s for 1.x. Since it uses lambdas the patch is not going to work for the 0.x branch. I don’t know what your plan for 0.8 is but I have a much less sophisticated patch for the for the 0.x branch. Should I

Re: ConsumeJMS and Acknowledgement Mode

Chris PR was submitted to the JIRA. Basically as I’ve commented in the JIRA I now do not believe we should be exposing any QOS options to the end user and instead implicitly ack messages only after they’ve been consumed by NiFi (i.e., transferred to a success relationship). Basically a classic