Re: Apache NiFi 1.0.0-BETA RC1 Release Helper Guide

Ok, I changed the authorizers.xml IAI to “OU=NiFi, CN=ca.nifi.apache.org” and it fails with the same message, so it does not appear to be a simple String comparison issue. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B

Re: Apache NiFi 1.0.0-BETA RC1 Release Helper Guide

After using Incognito browsers and re-importing the CA certificate as a client cert, I was able to connect to the app through the browser, but the authorization does not seem to be working: logs/nifi-user.log 2016-08-05 17:19:42,904 INFO [main] o.a.nifi.authorization.FileAuthorizer Populating

Re: Apache NiFi 1.0.0-BETA RC1 Release Helper Guide

Joe, I was able to verify all signatures, build, verify the contrib-check, and start an unsecured instance and use it as normal. However, when I attempted to deploy secured instances (using the tool contributed in NIFI-2193), I encountered issues with authentication. Steps to recreate: 1.

Re: [E] Apache NiFi 1.0.0-BETA RC1 Release Helper Guide

I believe Bryan Rosander also encountered issues with this test earlier in the week and there was concern it is non-deterministic? I don’t have the notes in front of me. He should be able to offer his recollections over the weekend or on Monday. Bryan Bende also committed a fix for the

Re: [E] Apache NiFi 1.0.0-BETA RC1 Release Helper Guide

After sending that email, I decided to just give the build another shot with the same command (mvn clean install -Pcontrib-check) and it worked with no errors. Not sure why it failed the first timeŠ - Kirk Tarou On 8/5/16, 3:24 PM, "Joe Percivall" wrote: >Hello, >

Re: [E] Apache NiFi 1.0.0-BETA RC1 Release Helper Guide

Hello, Thanks for taking the time to help validate the release but I am not able to reproduce those errors (these tests run fine for me). Can you provide some more information about your system or how you're running the tests? Thanks, Joe - - - - - - Joseph Percivall

Re: [E] Apache NiFi 1.0.0-BETA RC1 Release Helper Guide

During build, tests failed on nifi-hdfs-processors. GetHDFSTest.testAutomaticDecompression:153 expected:<1> but was:<0> GetHDFSTest.testFileExtensionNotACompressionCodec:191 expected:<1> but was:<0> GetHDFSTest.testGetFilesWithFilter:136 expected:<4> but was:<0>

Re: [DISCUSS] MiNiFi C++ Initial Release - cpp-0.0.1

+1 ! On Thu, Aug 4, 2016 at 11:42 PM, Aldrin Piri wrote: > Hey folks, > > There's been great efforts to get an initial working implementation of > MiNiFi in C++. This currently provides a great start on the core > functionalities that the Java equivalent provides.

Apache NiFi 1.0.0-BETA 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 1.0.0-BETA (RC1)

Hello Apache NiFi Community, I am pleased to be calling this vote for the source release of Apache NiFi, nifi-1.0.0-BETA. The source zip, including signatures, digests, etc. can be found at: https://repository.apache.org/content/repositories/orgapachenifi-1089/ The Git tag is

Re: ExecuteSQL returns empty avro file

Nabegh, I took a quick look at the code, and it looks like that is the expected behavior. There should be a flowfile attribute "executesql.row.count" that contains the number of rows. You could always route on that attribute to handle those empty result sets differently than ones that have one

Re: ExecuteSQL returns empty avro file

This is the expected behavior. There was a discussion on the dev@ mailing list about whether or not it should output anything at all in that case. The case was made that it is sometimes beneficial to know that the query did run and that no results were found. If you want to filter out these

Re: [DISCUSS] MiNiFi C++ Initial Release - cpp-0.0.1

+1, the possibilities this opens up are immense! On Fri, Aug 5, 2016 at 2:12 PM Andy LoPresto wrote: > Andy++ > > Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com * > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B

ExecuteSQL returns empty avro file

When no records are returned from the SQL statement, ExecuteSQL returns an avro file that contains the schema with no data. Is this the expected behaviour? Thanks. -- View this message in context:

Re: [DISCUSS] MiNiFi C++ Initial Release - cpp-0.0.1

Andy++ Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Aug 5, 2016, at 7:28 AM, Mark Payne wrote: > > I would be a +1. Very cool to see this reaching this stage! > >> On Aug 4, 2016,

Re: [DISCUSS] 1.0 Beta Release

Team, Glad to hear everyone is on board with a Beta. Sorry for not putting out an update earlier but I've been waiting to initiate the vote in order to get the all of the lingering framework level feature/improvement tickets in. The last one should be wrapping up shortly so look out for an RC

Re: [DISCUSS] 1.0 Beta Release

I've been playing with 1.x in the evenings, trying to understand the REST API and it's documentation for NIFI-2237 . I really like what I've seen so far, so I thought I'd toss out some observations before they slip away forever. The finer grained

Re: [DISCUSS] MiNiFi C++ Initial Release - cpp-0.0.1

I would be a +1. Very cool to see this reaching this stage! > On Aug 4, 2016, at 11:42 PM, Aldrin Piri wrote: > > Hey folks, > > There's been great efforts to get an initial working implementation of > MiNiFi in C++. This currently provides a great start on the core >

Re: [DISCUSS] MiNiFi C++ Initial Release - cpp-0.0.1

+1 a fantastic step forward. Will be great to see how close the the true edge this can go ;) On Fri, Aug 5, 2016 at 2:17 AM, Pierre Villard wrote: > +1, awesome! > > 2016-08-05 6:16 GMT+02:00 Matt Burgess : > > > +1, also we need documentation

Re: [DISCUSS] MiNiFi C++ Initial Release - cpp-0.0.1

+1, awesome! 2016-08-05 6:16 GMT+02:00 Matt Burgess : > +1, also we need documentation on the S2S protocol so we can further > extend the reach (Go, Python, Erlang/Elixir, etc) > > > > On Aug 4, 2016, at 11:42 PM, Aldrin Piri wrote: > > > > Hey folks,