Understood. Thanks very much Juan.
On Wed, Apr 12, 2017 at 1:24 PM, Juan Sequeiros wrote:
> We currently have a solid dev / prod environment and when ready we import
> the template from dev in to prod.
> We also have updated central processors that can't be replaced by a
> template with rest cal
We currently have a solid dev / prod environment and when ready we import
the template from dev in to prod.
We also have updated central processors that can't be replaced by a
template with rest calls.
But in general NIFI 1 is a massive upgrade to U/I, and this feature and
user policies from a ope
Okay thanks Joe. And I apologize: it seems you have mentioned that before.
On Wed, Apr 12, 2017 at 1:09 PM, Joe Witt wrote:
> Hello
>
> This has been addressed in NiFi 1.x. You can have multiple writers to
> various things in parallel and it handles it nicely.
>
> Thanks
> Joe
>
> On Wed, Apr 1
Hello
This has been addressed in NiFi 1.x. You can have multiple writers to
various things in parallel and it handles it nicely.
Thanks
Joe
On Wed, Apr 12, 2017 at 12:03 PM, James McMahon wrote:
> We have multiple people working is separate distinct processor groups under
> a common NiFi insta
We have multiple people working is separate distinct processor groups under
a common NiFi instance. As would be expected, they are often making changes
to their processor group workflows concurrently.
There are long periods of time where Betty loses any attempted changes
including reposition of pr
