Re: [VOTE] Release Apache NiFi 1.6.0

2018-03-23 Thread Sivaprasanna
Yeah. Tested and found the bug when using the Schema Registry service. I have made the changes and raised PR #2581 I have tested that both the scenario works as expected: 1. Original reason why the ticket was raised i.e. to reload new resources

Re: [VOTE] Release Apache NiFi 1.6.0

2018-03-23 Thread Pierre Villard
-1 (binding) I confirm the issue mentioned by Bryan. That's actually what Matt and I experienced when trying the PR about the S2S Metrics Reporting task [1]. I thought it was due to my change but it appears it's not the case. [1] https://github.com/apache/nifi/pull/2575 2018-03-23 22:53

Re: SOAP Service through InvokeHTTP

2018-03-23 Thread Code Novice
I've only just subscribed to the dev@nifi.apache.org mailing list and today was my first time even knowing that a thing like 'maling lists' existed. Regardless, I'm posting my question in hopes to seek out how you eventually managed to get your InvokeHTTP Processor to work with SOAP as I have not

Re: [VOTE] Release Apache NiFi 1.6.0

2018-03-23 Thread Bryan Bende
After voting I happened to be using the RC to test something else and came across a bug that I think warrants changing my vote to a -1. I created a simple two node cluster and made a standard convert record flow. When I ran the flow I got a schema not found exception, so I used the debugger which

Objection: LDAP Auth needs HTTPS

2018-03-23 Thread Qcho
Hi, I'm working on deploying a nifi cluster with kubernetes. The idea was to place a nifi-cluster behind an nginx-ingress. We want to be able to access: nifi.mydomain.com and allow load-balancing over: node1.nifi.mydomain.com node2.nifi.mydomain.com ... etc The problem here is that we want

Re: [VOTE] Release Apache NiFi 1.6.0

2018-03-23 Thread Matt Gilman
+1 (binding) Release this package as nifi-1.6.0 Executed the release helper and verified new granular restrictions with regards to flow versioning. Thanks for RMing Joe! Matt On Fri, Mar 23, 2018 at 4:12 PM, Michael Moser wrote: > +1 (binding) > > Ran through release

Re: NiFi Versioned Process Group Status Icons

2018-03-23 Thread Matt Gilman
Peter, The status icon for a specific Process Group is hidden until that group is versioned. That icon is positioned next to the group name. For the icons in the status bar and in the bottom of the Process Group, we were ultimately just trying to remain consistent. These reflect the counts of

Re: [VOTE] Release Apache NiFi 1.6.0

2018-03-23 Thread Michael Moser
+1 (binding) Ran through release helper to verify the release and run NiFi on Ubuntu 16.04. It worked as expected with no new comments to add. -- Mike On Fri, Mar 23, 2018 at 4:02 PM, Scott Aslan wrote: > +1 (binding) > > - Ran through release helper > - Setup secure

Re: [VOTE] Release Apache NiFi 1.6.0

2018-03-23 Thread Scott Aslan
+1 (binding) - Ran through release helper - Setup secure NiFi and verified a test flow On Fri, Mar 23, 2018 at 3:29 PM, Bryan Bende wrote: > +1 (binding) > > - Ran through release helper and everything checked out > - Verified some test flows with the restricted components +

Re: [VOTE] Release Apache NiFi 1.6.0

2018-03-23 Thread Bryan Bende
+1 (binding) - Ran through release helper and everything checked out - Verified some test flows with the restricted components + keytab CS On Fri, Mar 23, 2018 at 2:42 PM, Mark Payne wrote: > +1 (binding) > > Was able to verify hashes, build with contrib-check, and start

Re: [VOTE] Release Apache NiFi 1.6.0

2018-03-23 Thread Mark Payne
+1 (binding) Was able to verify hashes, build with contrib-check, and start up application. Performed some basic functionality tests and all worked as expected. Thanks! -Mark > On Mar 23, 2018, at 6:02 AM, Takanobu Asanuma wrote: > > Thanks for all your efforts, Joe.

Master failing in travis

2018-03-23 Thread Otto Fowler
Anyone have an idea why Master is failing in travis?

Re: FlattenJson

2018-03-23 Thread Bryan Bende
Most of the ideas discussed here are assuming there is one record per flow file, which for any serious amount of data is not what you want to do. It might be better to have a new ExtractJsonToAttributes processor that enforces limitations like a single json doc per flow file and all flat fields,

Re: FlattenJson

2018-03-23 Thread Jorge Machado
So I’m pretty lost now, all the suggestions from Matt will not solve my problem that I need to have all contents of a flow file as attritube key -paired… A good place to have it would be on ConvertAvroToJSON so that it has a option to say if it goes to attribute or to FlowFile, defaulting to

RE: [VOTE] Release Apache NiFi 1.6.0

2018-03-23 Thread Takanobu Asanuma
Thanks for all your efforts, Joe. I have one question. The version of the generated package is nifi-1.7.0-SNAPSHOT. Is this correct at this stage? If it's ok, +1(non-binding). - Succeeded "mvn -T 2.0C clean install -DskipTests -Prpm" - Started secure cluster mode - Verified sample dataflows