RE: [EXT] Re: [VOTE] Create NiFi Standard Libraries sub-project

+1, binding -Original Message- From: Kevin Doran Sent: Tuesday, September 3, 2019 7:12 PM To: dev@nifi.apache.org; dev@nifi.apache.org Subject: [EXT] Re: [VOTE] Create NiFi Standard Libraries sub-project +1, binding From: Tony Kurc Sent: Tuesday,

Re: [VOTE] Create NiFi Standard Libraries sub-project

+1, binding From: Tony Kurc Sent: Tuesday, September 3, 2019 8:33 PM To: dev@nifi.apache.org Subject: Re: [VOTE] Create NiFi Standard Libraries sub-project +1 (binding) On Wed, Sep 4, 2019 at 12:29 AM Aldrin Piri wrote: > +1, binding > > On Tue, Sep 3, 2019

Re: File-based Versioned Flow Representation

I will throw a vote for JSON-based representation moving forward as well, with the understanding that we now have three different codebases which convert from a serialized, human-readable format (XML, YAML, JSON) into the hydrated flow state object and back, and we should ensure through unit,

Re: [VOTE] Create NiFi Standard Libraries sub-project

+1 (binding) On Wed, Sep 4, 2019 at 12:29 AM Aldrin Piri wrote: > +1, binding > > On Tue, Sep 3, 2019 at 19:46 Yolanda Davis > wrote: > > > +1 Create NiFi Standard Libraries (binding) > > > > On Tue, Sep 3, 2019 at 7:03 PM Koji Kawamura > > wrote: > > > > > +1 Create NiFi Standard Libraries

Re: [VOTE] Create NiFi Standard Libraries sub-project

+1, binding On Tue, Sep 3, 2019 at 19:46 Yolanda Davis wrote: > +1 Create NiFi Standard Libraries (binding) > > On Tue, Sep 3, 2019 at 7:03 PM Koji Kawamura > wrote: > > > +1 Create NiFi Standard Libraries (binding) > > > > On Wed, Sep 4, 2019 at 7:25 AM Mike Thomsen > > wrote: > > > > > > +1

Re: [VOTE] Create NiFi Standard Libraries sub-project

+1 Create NiFi Standard Libraries (binding) On Tue, Sep 3, 2019 at 7:03 PM Koji Kawamura wrote: > +1 Create NiFi Standard Libraries (binding) > > On Wed, Sep 4, 2019 at 7:25 AM Mike Thomsen > wrote: > > > > +1 binding > > > > On Tue, Sep 3, 2019 at 5:33 PM Andy LoPresto > wrote: > > > > > +1,

Re: [VOTE] Create NiFi Standard Libraries sub-project

+1 Create NiFi Standard Libraries (binding) On Wed, Sep 4, 2019 at 7:25 AM Mike Thomsen wrote: > > +1 binding > > On Tue, Sep 3, 2019 at 5:33 PM Andy LoPresto wrote: > > > +1, create NiFi Standard Libraries (binding) > > > > Andy LoPresto > > alopre...@apache.org > > alopresto.apa...@gmail.com

Re: [VOTE] Create NiFi Standard Libraries sub-project

+1 binding On Tue, Sep 3, 2019 at 5:33 PM Andy LoPresto wrote: > +1, create NiFi Standard Libraries (binding) > > Andy LoPresto > alopre...@apache.org > alopresto.apa...@gmail.com > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > On Sep 3, 2019, at 2:16 PM, Bryan Bende

Re: [VOTE] Create NiFi Standard Libraries sub-project

+1, create NiFi Standard Libraries (binding) Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Sep 3, 2019, at 2:16 PM, Bryan Bende wrote: > > All, > > In a previous thread there was a plan discussed to

[VOTE] Create NiFi Standard Libraries sub-project

All, In a previous thread there was a plan discussed to restructure some of the repositories in order to address several different issues, such as build time, reusability of code, and eventually separating how the framework and extensions are released [1][2]. The overall plan requires many steps

Re: nifi deploy automation - variables pass through (incl controller services)

The short answer is - please revisit all of this after the 1.10.0 release because all of this will be solved with the new parameters feature :) Longer answer... The CLI has two commands: nifi pg-get-vars nifi pg-set-var These can be used to get and set process group level variables, which can

Re: nifi deploy automation - variables pass through (incl controller services)

There is a CLI command to change variables ... ? I've moved most of my processor variables to extra-args.property, so it's easy to change them. But there are a few I can't change - for example, DistributedMapCacheClientService controller service has a "Server Hostname" property that doesn't

Re: ValidateXML Schema File EL scope

It was likely just a decision by the developer of the processor, but in the current implementation you can parse the schema once when the processor is started which will be a lot more efficient then parsing every time the processor executes. If we do support flow file attributes then it could

IPV6 support

Hi , May I know when (which release)is ipv6 support planned for the Nifi . Thanks & Regards Ganesh.B

ValidateXML Schema File EL scope

We are using Apache NiFi 1.9.2 for one of our flows and had a question below. Why does the ValidateXML processor Schema File property supports only Variable registry in Expression Language scope? We are trying to devise a solution for our flow so that based on the incoming file name and

回复: CaptureChangeMySQL bit(1) type field is parsed to '{}'

Anybody has any insight on this? wangl...@geekplus.com.cn 发件人： wangl...@geekplus.com.cn 发送时间： 2019-08-22 19:31 收件人： users 主题： CaptureChangeMySQL bit(1) type field is parsed to '{}' CaptureChangeMySQL -> ConvertJSONToSQL -> ExecuteSQL to replicate my database. But when the field type is bit,

Re: nifi deploy automation - variables pass through (incl controller services)

Using the REST API to set a property was meant only for sensitive properties since they cant use variables. Changes to sensitive properties do not produce a change that is tracked by version control. All of this will be unnecessary with the new parameters functionality in 1.10.0. On Mon, Sep 2,

Apache NiFi contributor access

Hi, I would like to get contributor access to Apache Nifi on JIRA. Can you please add me to contributor list? My username is 'b.ganesh' . Thanks & Regards, Ganesh.B