Re: Regarding all queue monitoring

I saw a doc https://community.cloudera.com/t5/Support-Questions/Monitoring-nifi-back-pressure-threshold-and-trigger-an-email/td-p/218516 It shows 404 url..So I am assuming it is removed on the latest release of NIFI On Fri, 3 Jul 2020 at 09:26, Midhun Mohan wrote: > Hi all, > > I was trying to

Regarding all queue monitoring

Hi all, I was trying to set up a queue monitoring mechanism, Which is generic.. Like if I add any new processor it should monitor that one also automatically. Currently I am doing it like manually creating a monitoring system for each queue which queues UUID hard corded, Which doesn't seem to be

Re: Retry on HTTP processor preserving order of flow file

Hi Eduardo, It seems success on 100% success scenario, but 50 % failure scenario it seems to be mixing up the sequence.. So do you have any other suggestion than using wait/notify . On Wed, 1 Jul 2020 at 05:53, Eduardo Fontes wrote: > Hi Mithun, > > First of all, did you verify if the sequence

Re: [discuss] 1.12.0 or 1.11.5...

...and just saw Bryans note. Do we need more work before kicking out reg release? On Thu, Jul 2, 2020 at 7:42 PM Joe Witt wrote: > 100% same page as Andy. Mark said later this week he will have some key > bits wrapped. Lets see where we are then. > > thanks > > On Thu, Jul 2, 2020 at 7:22 PM

Re: [discuss] 1.12.0 or 1.11.5...

I think we probably want to consider releasing NiFi Registry 0.7.0 first. We have to do that in order to save versioned flows containing the new process group concurrency controls, otherwise the config would get lost when saved to registry. This is the nifi side PR that can’t be merged until a new

Re: [discuss] 1.12.0 or 1.11.5...

100% same page as Andy. Mark said later this week he will have some key bits wrapped. Lets see where we are then. thanks On Thu, Jul 2, 2020 at 7:22 PM Andy LoPresto wrote: > Martin, > > I understand everyone is anxious to get their hands on the next release, > but this thread is exactly how

Re: [DISCUSS] rename master branch, look through code for other related issues

Didn't see any commits or PRs for any of these yet. Do we want to consider these blockers for 1.12 or hold off until a post 1.12 release? On Mon, Jun 22, 2020 at 12:48 PM Joe Witt wrote: > Not that I'm aware of. All this so far just looks really easy to deal > with. > > On Mon, Jun 22, 2020 at

Re: [discuss] 1.12.0 or 1.11.5...

Martin, I understand everyone is anxious to get their hands on the next release, but this thread is exactly how we determine what will be in it. There is an inherent balance in determining which features and fixes need to be included to make the release worth it and which will delay it, and thi

Re: [discuss] 1.12.0 or 1.11.5...

** that's not to say I'll try to hold up a release vote over it, but there is a good reason behind asking that it be included in the last round of reviews. On Thu, Jul 2, 2020 at 10:07 PM Mike Thomsen wrote: > #4217 is something I need because I'm planning to build a Cassandra-based > Distribute

Re: [discuss] 1.12.0 or 1.11.5...

#4217 is something I need because I'm planning to build a Cassandra-based DistributedMapCache service for my client and contribute it back once we determine that it's stable enough to give back. On Thu, Jul 2, 2020 at 9:26 PM Martin Ebert wrote: > Hi Mike, > I suggest we wrap this up and only in

Re: [discuss] 1.12.0 or 1.11.5...

Hi Mike, I suggest we wrap this up and only include your PRs in version 1.13 Are there any objections to release NiFi 1.12? We should not keep the community waiting any longer. Best, Martin Mike Thomsen schrieb am Mi., 10. Juni 2020, 00:14: > I would like to refactor the OAuth2TokenProvider con

Could I get a review on this?

https://github.com/apache/nifi/pull/4217 Adds a putAll method to the distributed map cache client so you can bulk load data efficiently. I updated the HBase and Redis implementations to use a List/mset respectively. Was hoping to have this in place soon because I have a use case requiring me to cr

Re: board report for July 2020

Great report, thanks for taking care of it Joe! Le mer. 1 juil. 2020 à 16:57, Joe Witt a écrit : > Team, > > Here is the board report I've submitted for the July meeting. > > Thanks as always for the great progress! > > > ## Description: > The mission of NiFi is the creation and maintenance of s

Re: Next release NiFi 1.12

Here is the discussion thread [1]. [1] https://lists.apache.org/thread.html/r2cfeda59f96613c9d1739f4f2a1fd83ab15a4ff77d4659154a45bcac%40%3Cdev.nifi.apache.org%3E Andy LoP

Re: Next release NiFi 1.12

Martin Youll need to subscribe to dev to see this but there is already a discuss thread for it. As I mentioned on slack we just need to do it. There was some items folks were trying to wrap. Thanks On Thu, Jul 2, 2020 at 6:20 AM Martin Ebert wrote: > Hi community, > there are so many great n

Next release NiFi 1.12

Hi community, there are so many great new features waiting to be made available to the whole community as NiFi 1.12 Are there any reasons to wait for a release?