Re: ReplaceText processor - $ symbol escaping done incorrectly

2016-10-03 Thread Asanka Sanjaya Herath
@james, Yes that was the problem. I changed "Regex Replace" to "Always Replace" and it worked fine. Thanks so much for the help. On Sat, Oct 1, 2016 at 12:27 AM, James Wing wrote: > In your ReplaceText processor, is the Replacement Strategy property set to > the default "Regex Replace"? You mig

RE: NiFi operational interface

2016-10-03 Thread Roger Marin
Hi Joe, You are absolutely right what we are really looking for is for a "Job oriented" model. I understand Nifi was not designed with this use case in mind but is this something that might be worked on in the future? One of the things we would like to see (coming from a Job scheduler such as

Re: NiFi operational interface

2016-10-03 Thread Joe Witt
Roger, For people coming to NiFi from traditional ETL/ELT systems we're seeing a couple patterns emerge. They tend to want to view each flow discretely and have used other systems that way and are trying to use NiFi that way. And they tend to want a variety of relational data/database type const

Re: flow.xm.gz not being archived to ./conf/archive in NiFi 0.6.1

2016-10-03 Thread Simon Tack
Mark, That explains it. Thank you. Simon -Mark Payne wrote: - To: users@nifi.apache.org From: Mark Payne Date: 10/03/2016 11:26AM Subject: Re: flow.xm.gz not being archived to ./conf/archive in NiFi 0.6.1 Simon, The ability to have NiFi automatically back up the flow was added i

Re: flow.xm.gz not being archived to ./conf/archive in NiFi 0.6.1

2016-10-03 Thread Mark Payne
Simon, The ability to have NiFi automatically back up the flow was added in 1.0. Previous to 1.0, you have the ability to manually archive the flow, but it is not done each time that the flow is modified. Thanks -Mark > On Oct 3, 2016, at 11:06 AM, Simon Tack wrote: > > Hello, > > I am usin

flow.xm.gz not being archived to ./conf/archive in NiFi 0.6.1

2016-10-03 Thread Simon Tack
Hello, I am using NiFi 0.6.1 and I am trying to get flow.xml.gz files archived to the ./conf/archive directory when I make changes to my flow, like adding a new process group, or renaming one. I am new to NiFi, but I believe that this feature should be on by default. It is working by default

Re: Processors on the fly for many sensor devices

2016-10-03 Thread Davy De Waele
Hi Andrew, We'd be happy to test and provide feedback. We have a use-case now with Nifi that we're in the process of implementing. If you have sources or binaries feel free to let me know. Regards, Davy On Fri, Sep 30, 2016 at 9:24 PM, Andrew Psaltis wrote: > Hi Davy, > Sorry for the slow

Re: NiFi operational interface

2016-10-03 Thread Corey Flowers
I think that if you were able to stop/start/configure via the summary page, it would give you the UI functionality that you are looking for, in terms of the stopping and starting of process groups from the UI. I also believe this would help for faster change times of individual processors. On Mon,

Re: NiFi operational interface

2016-10-03 Thread Pierre Villard
In the Summary view, you have a tab "Process Group" but given the number of process groups you have it may not be ideal. In your situation, I guess, leveraging the REST API is probably the best way to go. Pierre 2016-10-03 10:19 GMT+02:00 Roger Marin < roger.ma...@colesfinancialservices.com.au>:

Re: NiFi operational interface

2016-10-03 Thread Roger Marin
Hi Pierre, Yes, the search toolbar in the canvas works but it seems to be searching across processors whereas what we really want to see is an interface centered around process groups. We encapsulate all of our etl/elt jobs in individual process groups based around a specific data source, henc

Re: NiFi operational interface

2016-10-03 Thread Pierre Villard
Hi Roger, I don't know if it answers your needs but you have a search tool bar to find any element on the canvas and quickly access it. In terms of monitoring, you have the "Summary" panel available from the menu. It gives you a way to quickly display information about everything on the canvas. P