the question about nifi cache auto clear default(5 min)

2018-07-13 Thread Xu, Zhi-Chao
Hi I found that in/out will be cleared after 5 min. the same as the report an = error/warn/debug But I don't' want it auto clear or I can change the time . I don't' found = configuration anywhere. How should I do ? Thank you very mach. Best Regards, Zhichao.xu

Dark mode

2018-07-13 Thread Rich M
Hi Going through some NiFi bits and pieces while I'm between projects; I've got a half-baked dark mode kicking around, is there any interest in me pushing this to a remote branch somewhere? There's some iframes in dialogs missing styling, it probably wants someone more familiar with Angular to loo

Re: Dark mode

2018-07-13 Thread Joe Witt
Rich This could certainly be an interesting option. Perhaps file a JIRA with some details on where you're at in your PR and post that when ready. Identify things you think might be remaining and such.. Thanks On Fri, Jul 13, 2018 at 7:25 AM, Rich M wrote: > Hi > > Going through some NiFi bits

Re: [VOTE] Release Apache NiFi 1.7.1

2018-07-13 Thread Peter Wilcsinszky
+1 However I can't see the release tag "nifi-1.7.1-RC1". curl -s https://github.com/apache/nifi/tree/nifi-1.7.1-RC1 -w '%{http_code}\n' -o /dev/null 404 vs: curl -s https://github.com/apache/nifi/tree/nifi-1.7.0-RC1 -w '%{http_code}\n' -o /dev/null 200 Is it really missing or will be tagged al

Re: [VOTE] Release Apache NiFi 1.7.1

2018-07-13 Thread Joe Witt
+1 (binding) verified full build with contrib check and all tests (linux and osx), sig, hashes, version, L&N, and last couple of commits included. Noted Peter's finding of the RC tag not being present but that is ok since the noted commit is. The real release tag will be pushed so that is ok. T

Re: Dark mode

2018-07-13 Thread Brandon DeVries
I think there are a lot of people that would be a big +1 on this. Maybe even more so if it was abstracted so there could be multiple / custom "themes" (e.g. dark, classic, high contrast / 508 compliant...). Brandon On Fri, Jul 13, 2018 at 7:29 AM Joe Witt wrote: > Rich > > This could certainly

RE: [EXT] Re: Dark mode

2018-07-13 Thread Peter Wicks (pwicks)
I did something similar back in 1.2.0 using CSS overrides and a chrome plugin : https://userstyles.org/styles/142978/dark-nifi-1-2-0. -Original Message- From: Brandon DeVries [mailto:b...@jhu.edu] Sent: Friday, July 13, 2018 9:42 AM To: dev@nifi.apache.org Subject: [EXT] Re: Dark mode

Re: [VOTE] Release Apache NiFi 1.7.1

2018-07-13 Thread James Wing
+1 (binding). Ran through the release helper, checked license, notice, readme files, and tested the resulting binary. Thanks for putting this together, Andy. On Thu, Jul 12, 2018 at 2:00 PM Andy LoPresto wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache

Re: [VOTE] Release Apache NiFi 1.7.1

2018-07-13 Thread Andy LoPresto
Peter, Thanks for validating. The tag was pushed to the official repository [1] but not mirrored to github yet. For the official release, it will be there. [1] https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=tag;h=411983dbafaaae8d76a2d7a4ae4b8d1177fae1eb

[DISCUSS] NiFi shared file system

2018-07-13 Thread Mark Bean
I'd like to start a discussion on making NiFi Clustering more robust. As it is, a Cluster is very beneficial from a management standpoint. A change only needs to be made in one place - any place - and it is replicated across the cluster. However, from a data perspective, the same flexibility is not

Re: [VOTE] Release Apache NiFi 1.7.1

2018-07-13 Thread Mark Payne
+1 (binding). Verified checksums and hashes. Verified full build with contrib-check. Verified that the app starts and provides the basic functionalities. Verified that wildcard certificates now work in clustered mode. Verified that the recursively referenced Controller Services now behave as expe

Re: [VOTE] Release Apache NiFi 1.7.1

2018-07-13 Thread Matt Gilman
+1 (binding) Verified signatures, hashes, build, etc. Ran into one minor thing that probably warrants a note in the migration guide. The certificates that I used in my cluster previously no longer work. It appears the issue is my fault because the certificates did not have the hostname properly s

Re: [VOTE] Release Apache NiFi 1.7.1

2018-07-13 Thread Andy LoPresto
Thanks Matt. I think that was a remnant of the hostname verifier implementation being switched from a local (incomplete) implementation to an externally provided one that is RFC 6125 compliant. I will add that to the migration guidance and open a follow-on ticket to NIFI-5399 to further update t

Re: [VOTE] Release Apache NiFi 1.7.1

2018-07-13 Thread Andrew Lim
+1 (non-binding) -Ran full clean install on OS X (10.11.6) -Tested integration with NiFi Registry (0.2.0) -Ran some basic flows; working as expected. -Reviewed documentation. Noticed that the doc added for wildcard certificates was included in master but not 1.7.1 [1] Drew [1] https://issues.

Re: [VOTE] Release Apache NiFi 1.7.1

2018-07-13 Thread Andy LoPresto
Thanks for catching that Drew. I missed cherry picking the commit into the release branch. I don’t think it rises to the level of canceling this release, but I will note in the release notes that the ticket is not included and add extra notes to the migration guidance. Andy LoPresto alopre...@