Re: setting processor concurrency based on the development/production environment

Kevin, The release cadence is a very loose schedule. Usually “point releases” (minor version upgrades) come approximately 10 - 14 weeks after the previous (i.e. 1.5.0 -> 1.6.0). In some cases, a bug fix release (1.5.0 -> 1.5.1) will be released on a shorter time frame if deemed necessary. As

Re: NiFI Maven Plugin - Timestamped Snapshot Version Problem

Hi Arne, Thanks for the detailed explanation, that is an interesting scenario, but I can see why it would be problematic. Can you file a NiFi JIRA with that write up and tag the component as "Nar-Maven-Plugin" ? Thanks, Bryan On Fri, Mar 2, 2018 at 12:02 PM, Arne Degenring

Re: setting processor concurrency based on the development/production environment

There are 2 efforts, with somewhat different focus. You are already aware of the community-driven nipyapi, but there's also an official module Ientioned before, will be included with the 1.6 release. Andrew On Fri, Mar 2, 2018, 8:59 AM Boris Tyukin wrote: > Hi Andrew, >

Re: NiFI Maven Plugin - Timestamped Snapshot Version Problem

Hi Mike, No, we are running standard NiFi 1.4.0 and are using the standard NiFi Maven plugin 1.2.0. We just have implemented a couple of custom processor and service NARs. Thanks Arne > On 2. Mar 2018, at 17:54, Mike Thomsen wrote: > > Are you by any chance running a

Re: NiFI Maven Plugin - Timestamped Snapshot Version Problem

Are you by any chance running a custom build of NiFi? On Fri, Mar 2, 2018 at 9:44 AM, Arne Degenring wrote: > Hi, > > > > We have seen a strange problem on NiFi 1.4.0 where custom processors could > suddenly not be started, because of incompatibility with custom

NiFI Maven Plugin - Timestamped Snapshot Version Problem

Hi, We have seen a strange problem on NiFi 1.4.0 where custom processors could suddenly not be started, because of incompatibility with custom services: 2018-03-02 13:40:35,490 ERROR [main] o.apache.nifi.controller.FlowController Unable to start …[id=5d57d39a-015c-1000--d654d90b] due

Re: List archive files before extration

Hey Kiran, It is possible to do in NIFI using ExecuteProcess processor. I would implement it as following: 1. Get the file from FS 2. Route on filename extension (tar.gz, zip, rar, etc). when you create relationships by adding expressions, you can use for example:

Re: Extract primary node hostname/ipaddress in the flow

Thanks, Bryan and Pierre that helps. On Thu, Mar 1, 2018 at 4:07 PM, Pierre Villard wrote: > Hi, > > There is the following JIRA: https://issues.apache.org/ > jira/browse/NIFI-1598 > > Pierre > > 2018-03-01 15:53 GMT+01:00 Bryan Bende : > >> Hello,

Re: setting processor concurrency based on the development/production environment

Opened NIFI-4921 better support for promoting NiFi processor parameters between dev and prod environments Thanks! On Thu, Mar 1, 2018 at 11:43 AM, Bryan Bende wrote: > Hello, > > Glad you are having success with NiFi + NiFi Registry! > > You brought up an interesting point

Re: setting processor concurrency based on the development/production environment

Hi Andrew, thanks for the idea. I've been playing with nipyapi recently so might give this a try. Thanks On Thu, Mar 1, 2018 at 7:32 PM, Andrew Grande wrote: > Boris, > > Here's an idea youncould explore _today_. > > Assume your dev and prod flows live in different

Re: Atlas and NiFi integration help

Bryan, That did it. It might not be able to answer at the granularity of how many times a reindex was done, but with the right mix of updateattributes and that task, I was able to build an ElasticSearch index that can at least show a date histogram aggregation of when reindex operations happened