Re: Closing in on a NiFi 1.2.0 release?

This is good discussion that should continue, but what about the original intent of Joe's post? "Is there any reason folks can think of to hold off on a 1.2.0 release?" On Fri, Mar 3, 2017 at 1:45 PM, Mark Payne wrote: > Andy, > > Sorry, i haven't responded to this thread

Re: Controller Services tab

Thanks for the replies. I understand now. I strongly support NIFI-3128 and its subtasks to avoid confusion. On Fri, Mar 3, 2017 at 8:54 AM, Matt Gilman wrote: > Joe, > > The different scoping of Controller Services was part of the multi-tenant > effort. The general

Re: Controller Services tab

Joe, The different scoping of Controller Services was part of the multi-tenant effort. The general idea was to establish points of limited availability to ensure the service usage does not become so broad that updating (including stopping and starting of all things that reference the service) is

Re: Closing in on a NiFi 1.2.0 release?

Andy, Sorry, i haven't responded to this thread in over a week, but I think it's important to keep going. I just clicked "Cancel Patch" on one of my ticket that has a patch available to see which state it returned to. It did in fact go back to Open. Which I agree is less than ideal. Though we

Re: Controller Services tab

Bryan, That makes sense, but I missed that subtly in the 0.x to 1.x changes. I ran into some questions while trying to get it straight in my head. * How do the global controller services differ from those in the root process group? * Are the global controller services only available to

NiFi processor for Google Drive

Hi, I want to access the files from google drive using NiFi processor. I would like to use in build processor rather writing a Custom Processor. Is the any in build processor available for google drive? Regards, Shankha -- View this message in context:

Re: Nifi on Raspberry pi - jetty issues

Hi, We have taken a look at MiNiFi, and the reason why we want to use NiFi still is because of the REST API that NiFi provides which we want to use to dynamically rewire the processors whenever needed without needing to halt all the processors in the graph. >From what I understand of MiNiFi,

Re: Nifi on Raspberry pi - jetty issues

Pushkar, I just realized after sending the email, that I did not provide any resources where you can learn more about MiNiFi outside of the Apache site. Here are some resources that may make your experience a little smoother: Edge Intelligence with MiNiFi --

Re: Nifi on Raspberry pi - jetty issues

Pushkar, While it certainly should and has been possible to run regular NiFi on a PI. Perhaps the best way forward is to actually use MiNiFi [1]. MiNiFi is available in as a C++ and Java agent and designed explicitly to run on devices. I'm sorry I could not be of more assistance with the actually