Re: MiNiFi logs not removed as per l maxHistory in ogback.xml

Thanks for quick support Aldrin. Yes I can evaluate 0.2 Sent from my iPhone > On May 15, 2017, at 12:38 PM, Aldrin Piri wrote: > > Just to close the loop, the issues referenced earlier are: > > https://issues.apache.org/jira/browse/MINIFI-144 >

Re: Apache NiFi 0.7.3 RC1 Release Helper Guide

I think we're good. We need his signing key is in the KEYS file at the time we publish the release. It sounds like we're on track for that - his key is checked into the git KEYS file, and someone has been enlisted to publish the KEYS file. I'm sorry to promote confusion, I wasn't sure what the

Re: Apache NiFi 0.7.3 RC1 Release Helper Guide

Joe, James, Mike, I think I got confused. Do we need to get Mike's gpg public key which he used to sign in that KEYS file, or is the key Mike put in the helper sufficient? If it isn't sufficient, we need someone with access to svn to add Mike, correct? Tony On Mon, May 15, 2017 at 4:34 PM,

Re: Apache NiFi 0.7.3 RC1 Release Helper Guide

Yeah, I didn't have write permission to SVN https://dist.apache.org/repos/dist/ which I assumed was because I'm a committer and not on the PMC. I've enlisted a PMC member's help to put the release up there if this vote passes. On Mon, May 15, 2017 at 3:13 PM, Joe Witt

Re: [VOTE] Release Apache NiFi 0.7.3

+1 - Ran through the release helper, verified hashes and signature (with provided mosermw.asc key). Full build succeeded. Ran a simple test flow. License, notice, readme all look good. Thanks for putting this release together. James On Sun, May 14, 2017 at 5:33 PM, Michael Moser

Re: Telescopic controller services in test framework...

Russ, When you call setProperty, it's expecting a String value, so you don't want to set the value of the property to `service2` but rather you'd set the property to the identifier for service2. For example: runner.addControllerService( "service-id2", service2 ); // add service2 with an

Re: Telescopic controller services in test framework...

I forgot, InvokeScriptedProcessor has an example of "dynamically" adding properties, the code is a bit weird but the idea is represented there:

Re: Telescopic controller services in test framework...

I believe NIFI-1121 [1] covers the ability for properties to depend on each other, it is still an open issue. I think the workaround is to override onPropertyModified(), and rebuild the dependent property based on the change in value(s). The user will have to hit the Apply button on the dialog

Re: MiNiFi logs not removed as per l maxHistory in ogback.xml

Just to close the loop, the issues referenced earlier are: https://issues.apache.org/jira/browse/MINIFI-144 https://issues.apache.org/jira/browse/MINIFI-173 The associated issues with logback, inclusive of what I believe you were experiencing, include: https://jira.qos.ch/browse/LOGBACK-1166

Re: Apache NiFi 0.7.3 RC1 Release Helper Guide

just need to update that dist key file is all. I think mike did update the git entry. On Mon, May 15, 2017 at 3:12 PM, James Wing wrote: > Michael, > > What's the plan for the PGP key distribution, or how do we get your key > into the KEYS file? > > Thanks, > > James > > On

Re: Apache NiFi 0.7.3 RC1 Release Helper Guide

Michael, What's the plan for the PGP key distribution, or how do we get your key into the KEYS file? Thanks, James On Sun, May 14, 2017 at 5:36 PM, Michael Moser wrote: > Hello Apache NiFi community, > > Please find the associated guidance to help those interested in >

Re: MiNiFi logs not removed as per l maxHistory in ogback.xml

Hi Sumanth, This was a product of some bugs with the log back library itself and have been remedied. On my phone currently but there are a couple JIRAs related to this. The new version currently under vote (0.2.0) should have these issues resolved since including newer releases of the logback

MiNiFi logs not removed as per l maxHistory in ogback.xml

We have an issue with MiNiFi (minifi-0.1.0 Java). It is not rotating its logs as per conf/logback.xml maxHistory value. Over the time, it is filling the drive and leaving many log files on desk. many "minifi-app.log15558502285619089.tmp" files are left on desk. please advice. Thanks Sumanth

Apache NiFi MiNiFi 0.2.0 RC1 Release Helper Guide

Hello Apache NiFi community, Please find the associated guidance to help those interested in validating/verifying the release so they can vote. # Download latest KEYS file: https://dist.apache.org/repos/dist/dev/nifi/KEYS # Import keys file: gpg --import KEYS # [optional] Clear out local

[VOTE] Release Apache NiFi MiNiFi 0.2.0

Hello, I am pleased to be calling this vote for the source release of Apache NiFi MiNiFi, minifi-0.2.0. The source zip, including signatures, digests, etc. can be found at: https://repository.apache.org/content/repositories/orgapachenifi-1107 The Git tag is minifi-0.2.0-RC1 The Git commit ID

Re: nifi.templats.directory

As of version 1.2.0, templates in the specified nifi.templates.directory location are not available via the UI until NiFi is restarted. Is this expected behavior? Or, as indicated previously, should the template(s) be loaded whenever the controller is saved? On Wed, Apr 19, 2017 at 12:31 PM,

Re: Partitioning from actual Data (FlowFile) in NiFi

Thank you so much for the reply! We have one more question regarding the whole flow - This entire flow described above has been encapsulated inside a template for export and import purpose in different environment. - Let's say one version of a Flow is running presently in PROD. -

Re: Partitioning from actual Data (FlowFile) in NiFi

Yes to compress. The output of the merge step is a larger piece of data, no more/older than configured by the merge step. It can produce partial smaller buckets if it were configured with max age attribute. Andrew On Mon, May 15, 2017, 5:28 AM Anshuman Ghosh wrote:

AWS ELB compatibility

Saw this issue in Jira. It seems pretty important and the fix would be relatively easy. I believe. https://issues.apache.org/jira/browse/NIFI-3882 Wouldn't the fix be to check for both the AWS provided http header and the existing ones to provide compatibility? That would fix the scheme and the