Re: Did 1.4.0 introduce a "breaking change" ?

Matt, I did some investigation and it seems like if you simply copy the old authorizers.xml into the new setup NiFi fails with ERROR [main] o.s.web.context.ContextLoader Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name

Re: Did 1.4.0 introduce a "breaking change" ?

Andre, While 1.4.0 introduces a more granular authorizers configuration, the existing 1.3.0 configurations should still be valid. What was breaking for you? Matt Sent from my iPhone > On Oct 30, 2017, at 10:24 PM, Andre wrote: > > Folks, > > I was looking at the

Did 1.4.0 introduce a "breaking change" ?

Folks, I was looking at the upgrade process from 1.3.x to 1.4.0 and it seems to me we introduced a breaking change around the authorizations? When I look at the 1.4.0 authorizers.xml and its version 1.3.0 there's a massive discrepancy on the XML tree and the existing 1.3.x version does not seem

Re: Nifi Embedded Zookeeper Ports

Grant, I’m not sure if this is what you are looking for, but in ZooKeeper version 3.3.0 and above [1], you can set the client port in the ZK configuration file. [1] https://zookeeper.apache.org/doc/trunk/zookeeperAdmin.html#sc_advancedConfiguration

Nifi Embedded Zookeeper Ports

In a firewall constrained environment is there a way to configure the Nifi embedded zookeeper to use static ports when connecting to server ports on other nodes? I am using the default ports for the server instances 2181, 2888, etc and am looking to statically define the ports used in connecting

Re: Two issues relating to a processor I'm developing

Mike, Regarding the licensing, I believe LGPL is a no-go for Apache projects. Take a look here: https://www.apache.org/legal/resolved.html#category-x -Bryan On Sat, Oct 28, 2017 at 4:47 PM, Mike Thomsen wrote: > The processor breaks down a much larger file into a huge

Re: Adding Failure handling to ListFile

We are run separate processes (implemented as Process Group) which have start and end. Same process should same unique id. We want to monitor process from start to end. Summary include only process name, when started, when ended, unique id and whatever it was successful or not. In case of failure

Re: Adding Failure handling to ListFile

toivo with all source processors there is the potential for failure. The challenge is what to capture and more generally what one would do with a flowfile representing not data but the fact of a failure. Can you share more of your thoughts on that for this case and perhaps generally? thanks

Re: Importing templates which have reference to same controller service.

1.3.0 -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: Adding Failure handling to ListFile

Content would be empty. One or more attributes contain error message, maybe error code, etc. -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: Importing templates which have reference to same controller service.

what version of nifi are you using? On Oct 30, 2017 8:53 AM, "Toivo Adams" wrote: > Hi > > Today we had annoying problem after importing template. > Template has reference to same controller service (with same name) which > already existed. > As result controller service

Importing templates which have reference to same controller service.

Hi Today we had annoying problem after importing template. Template has reference to same controller service (with same name) which already existed. As result controller service list shows 2 services with same name and one was disabled. One processors from new flow complained what controller

Re: Adding Failure handling to ListFile

Toivo What would be sent to FAILURE? What is the content or attributes of the flowfile in that case? Thanks On Mon, Oct 30, 2017 at 8:42 AM, Toivo Adams wrote: > Hi > > ListFile has only SUCCESS relationship. > > It would useful to add also FAILURE. > For example when

Adding Failure handling to ListFile

Hi ListFile has only SUCCESS relationship. It would useful to add also FAILURE. For example when input directory does not exist or can’t be read. What do you think? Thanks Toivo -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Adding EL support to UpdateAttribute for the Attribute Name

I've run into a use case for adding EL support into the Attribute Name itself in UpdateAttribute. Looking for thoughts on other approaches, pros/cons of doing this. I'm generically extracting data from a database. Right now I have ~30 tables, but that number could be anything, just think big