Re: Required work to close out 1.10

2019-07-29 Thread Mike Thomsen
FWIW I'm 100% in favor of waiting until we can get both fully working on Java 11. On Mon, Jul 29, 2019 at 3:44 PM Jeff wrote: > Another thought might be to get NiFi Registry builds on Java 11 working as > well for the NiFi Registry 0.5.0 release. With the NiFi Java 11 build > compatibility

Re: Required work to close out 1.10

2019-07-29 Thread Jeff
Another thought might be to get NiFi Registry builds on Java 11 working as well for the NiFi Registry 0.5.0 release. With the NiFi Java 11 build compatibility close to being merged, it should be much more simple to get NiFi Registry building on Java 11. It would be good to release versions for

Re: Record path API chooses CHOICE[STRING, RECORD] when the field is missing

2019-07-29 Thread Mark Payne
Mike, What Record Reader is being used here? The problem appears to be due to the Record Reader itself assigning that as the field type. I created a dummy unit test to verify the RecordPath stuff is correct: @Test public void testFromEmail() { final List fields = new ArrayList<>();

Re: Required work to close out 1.10

2019-07-29 Thread Andy LoPresto
There are also a number of new features around encrypted repositories and encrypted configuration values that would be good to get in. Some have active PRs up right now, and others are close to being posted. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC

Re: Required work to close out 1.10

2019-07-29 Thread Bryan Bende
There are two really helpful bug fixes [1][2] related to version controlling flows that I would like to see make it in to 1.10.0, but they are dependent on releasing registry 0.5.0 first, since part of the fixes are in the registry flow-diff code which NiFi depends on. So I was hoping to release