Re: [EXT] Re: [DISCUSS} Closing in on a NiFi 1.4.0 release?

2017-09-19 Thread Koji Kawamura
Hi Paul, I was able to reproduce the GenerateTableFetch processor issue reported by NIFI-4395. Please go ahead and provide a PR, I can review it. Thanks, Koji On Wed, Sep 20, 2017 at 1:10 PM, Paul Gibeault (pagibeault) wrote: > We have submitted this JIRA ticket: >

RE: [EXT] Re: [DISCUSS} Closing in on a NiFi 1.4.0 release?

2017-09-19 Thread Paul Gibeault (pagibeault)
We have submitted this JIRA ticket: https://issues.apache.org/jira/browse/NIFI-4395 This issue causes GenerateTableFetch processor to malfunction after a server restart. We are very interested in getting this released in 1.4.0 and are willing to provide the PR if there is still time. Thanks,

Re: Separate MiNiFi projects in JIRA

2017-09-19 Thread Aldrin Piri
One final note, is that I intend to move all CPP related issues to this tracker. The full thought process is captured on the JIRA [1]. In quick summary though, JIRA will redirect all issues to their new location/issue and versions are getting mapped to those in the MINIFICPP project without the

Re: Separate MiNiFi projects in JIRA

2017-09-19 Thread Jeff Zemerick
Great! Thanks! On Tue, Sep 19, 2017 at 9:56 AM, Aldrin Piri wrote: > Hey folks, > > The new JIRA project is now live. Please make use of that when filing C++ > related JIRAs. I am going to start moving appropriate items to that > instance. > > On Mon, Sep 4, 2017 at 2:13

Re: Separate MiNiFi projects in JIRA

2017-09-19 Thread Andy Christianson
Glad to hear it! Thanks for taking the time. -Andy I.C. On 9/19/17, 9:57 AM, "Aldrin Piri" wrote: Hey folks, The new JIRA project is now live. Please make use of that when filing C++ related JIRAs. I am going to start moving appropriate items to that

Re: "Flatten" JSON

2017-09-19 Thread Nicholas Hughes
Created an issue for this functionality [1]. Please change issue properties and comment as necessary. -Nick [1] https://issues.apache.org/jira/browse/NIFI-4398 On Sat, Sep 16, 2017 at 4:55 PM, Matt Burgess wrote: > +1 for FlattenRecord as well. In the meantime you can

Re: HBase security label support

2017-09-19 Thread Mike Thomsen
I started working on this and have PutHBaseCell, PutHBaseJSON and FetchHBaseRow working with it. I'm following a loose convention that goes like this: 1. Option of sane default for visibility boolean string where appropriate, but the string is not required. 2. User defines the list of tokens that