Re: Variables to start a NiFi flow

2019-08-29 Thread Bronislav Jitnikov
Variable Registry it is not what you need as I think. In similar case I generate flow files with tables in Atribute that I need to scan and pass it as upstream to SQL Processor. For example. GenerateFlowFile (list of tables in content) (Or Read list of tables from File, Varibale registry etc..)

Re: [discuss] approaching a NiFi 1.10.0 release

2019-08-29 Thread Aldrin Piri
I created NIFI-6604 [1] to reduce assembly size and listed it as a Blocker for this release. The issue has a link to the associated discussion thread and an initial PR. --aldrin [1] https://issues.apache.org/jira/browse/NIFI-6604 On Thu, Aug 29, 2019 at 4:08 PM Matt Burgess wrote: > Mike, >

Re: [discuss] approaching a NiFi 1.10.0 release

2019-08-29 Thread Koji Kawamura
There is a critical issue with RAW Site-to-Site server side code with Java 11. RAW Site-to-Site cannot be used currently due to the illegal blocking mode error. https://issues.apache.org/jira/browse/NIFI-5952 There is a PR to make RAW S2S not using blocking mode. This addresses the issue and RAW

Re: MiNiFi Python Dependencies (Anaconda)

2019-08-29 Thread Marc Parisi
Hi Jeremy, The env variable I sent can be set or appended prior to running minifi, without the need to recompile. On Thu, Aug 29, 2019, 3:38 PM Jeremy Dyer wrote: > So are you saying I need to build and link against my conda python binary? > > On Thu, Aug 29, 2019 at 6:47 AM Marc Parisi

Re: [discuss] approaching a NiFi 1.10.0 release

2019-08-29 Thread Matt Burgess
Mike, I’ll review those two graph PRs tonight or tomorrow (if they’re still open by then) > On Aug 29, 2019, at 3:43 PM, Mike Thomsen wrote: > > I have two open graph-related PR's that are really small and are needed to > close some bugs that will be bad for early adopters: > >

Re: [discuss] approaching a NiFi 1.10.0 release

2019-08-29 Thread Mike Thomsen
I have two open graph-related PR's that are really small and are needed to close some bugs that will be bad for early adopters: https://github.com/apache/nifi/pull/3571 https://github.com/apache/nifi/pull/3572 If someone wants to review, that'd be great. Otherwise, I can merge them in because

Re: MiNiFi Python Dependencies (Anaconda)

2019-08-29 Thread Jeremy Dyer
So are you saying I need to build and link against my conda python binary? On Thu, Aug 29, 2019 at 6:47 AM Marc Parisi wrote: > Hi Jeremy, > > Apache NiFi MiNiFi C++ python processors support virtual environments; > however, I don't think the library links, once the binary is built, will be >

Re: [discuss] approaching a NiFi 1.10.0 release

2019-08-29 Thread Joe Witt
We had another discuss on that recently and the intent is to drop a few toys off the raft and update migration guidance. Thanks On Thu, Aug 29, 2019 at 2:02 PM Jeremy Dyer wrote: > +1 looking forward to this. > > I recall seeing some issues about Apache Infra and the binary size. Were > all of

Re: [discuss] approaching a NiFi 1.10.0 release

2019-08-29 Thread Jeremy Dyer
+1 looking forward to this. I recall seeing some issues about Apache Infra and the binary size. Were all of those appropriate modules removed as discussed and the build size will be small enough now? On Thu, Aug 29, 2019 at 1:35 PM Bryan Bende wrote: > +1 Looking forward to getting parameters

Re: [discuss] approaching a NiFi 1.10.0 release

2019-08-29 Thread Bryan Bende
+1 Looking forward to getting parameters and Java 11 support out there in a release. On Thu, Aug 29, 2019 at 1:02 PM Joe Witt wrote: > > Team, > > It looks like we're reaching a point in which it is time to close in on > 1.10. > >

[discuss] approaching a NiFi 1.10.0 release

2019-08-29 Thread Joe Witt
Team, It looks like we're reaching a point in which it is time to close in on 1.10. https://issues.apache.org/jira/browse/NIFI-6595?jql=project%20%3D%20NIFI%20AND%20fixVersion%20%3D%201.10.0 There are 250+ issues in there nearly 240 of which are already resolved. I haven't gone through yet for

Re: MiNiFi Python Dependencies (Anaconda)

2019-08-29 Thread Marc Parisi
Hi Jeremy, Apache NiFi MiNiFi C++ python processors support virtual environments; however, I don't think the library links, once the binary is built, will be overridden through conda's environment activation ( only PATH is updated if I recall correctly ) I could be off base on the problem