RE: Loaded template cache

group. Thanks, Bryan On Thu, Apr 16, 2020 at 4:52 PM William Gosse mailto:william.go...@aifoundry.com>> wrote: Before I start up Nifi I removed all the _repository folders in order to remove any remnant data such as flow files in queues. One thing I notice that doesn’t get cleared up a

Loaded template cache

Before I start up Nifi I removed all the _repository folders in order to remove any remnant data such as flow files in queues. One thing I notice that doesn’t get cleared up are old copies of the loaded templates. I have to use nifi’s api to do that. Is there place where the loaded templates

RE: DistributedMapCacheService - automated creation

eation [CAUTION: This email originated from outside of Kodak Alaris. Do not click links or open attachments unless you recognize the sender and know the content is safe.] Anything you can do from the UI goes through the REST API. You can open Chrome Dev

RE: DistributedMapCacheService - automated creation

like something that you could implement implicitly with the HBase version by just creating one big cache table with an eye for not overlapping column qualifiers and possibly liberal use of HBase TTLs. On Tue, Jan 14, 2020 at 6:04 PM William Gosse mailto:william.go...@aifoundry.com>>

DistributedMapCacheService - automated creation

Is there any way to automate the creation of a DistributedMapCacheService I was hoping I could do this via a template but it doesn’t to get exported the way the DistributedMapCacheClientService does. The client got created just fine but there’s no service. I don’t see away to do this with

Check if a Flowfile is already running

Is there a way to check if there is any existing flowfile with a specific attribute value already running. I’m running a schedule task that starts the processing of a flowfile. If a flowfile with a certain value I want to terminate processing of the new file.

RE: Need help with DetectDuplicate

William Gosse, mailto:william.go...@aifoundry.com>> wrote: I’m trying to use DetectDuplicate processor but not having much luck. Here the config: Cache Entry Identifier ${resourceId} FlowFile Description Ingestion Age Off Duration 60 sec Cache The Entry Identifier true Distributed Cache S

Need help with DetectDuplicate

I’m trying to use DetectDuplicate processor but not having much luck. Here the config: Cache Entry Identifier ${resourceId} FlowFile Description Ingestion Age Off Duration 60 sec Cache The Entry Identifier true Distributed Cache Service DistributedMapCacheClientService I created abd enabled a

RE: HandleHTTPRequest 503 error issue

I’ve seen the same issue in 1.92 as well and opened the following ticket for it:

RE: HandleHttpRequest - Failed to receive content from HTTP Request

working for any reason if possible especially for something like a client dropping its connection. From: William Gosse Sent: Friday, September 13, 2019 8:33 AM To: users@nifi.apache.org Subject: RE: HandleHttpRequest - Failed to receive content from HTTP Request [CAUTION: This email originated

RE: HandleHttpRequest - Failed to receive content from HTTP Request

. If the this value is exceeded the HandleHttpRequest hangs up. In this specific issue that time out also was reached but it seems that the flow never got beyond the HandleHttpRequest. From: William Gosse Sent: Tuesday, September 10, 2019 5:14 PM To: users@nifi.apache.org Subject: RE

RE: HandleHttpRequest - Failed to receive content from HTTP Request

sept. 2019 à 08:09, William Gosse mailto:william.go...@aifoundry.com>> a écrit : It’s 1.9.2 From: Pierre Villard mailto:pierre.villard...@gmail.com>> Sent: Monday, September 9, 2019 7:43 PM To: users@nifi.apache.org<mailto:users@nifi.apache.org> Subject: Re: HandleHttpRequest -

RE: HandleHttpRequest - Failed to receive content from HTTP Request

recognize the sender and know the content is safe.] Hey William, Which version of NiFi are you using? Pierre Le lun. 9 sept. 2019 à 16:20, William Gosse mailto:william.go...@aifoundry.com>> a écrit : I have had couple occurrence of the following exception occ

HandleHttpRequest - Failed to receive content from HTTP Request

I have had couple occurrence of the following exception occurring on an HandleHttpRequest pprocessor: nifi-app_2019-09-06_12.0.log:2019-09-06 12:24:48,132 ERROR [Timer-Driven Process Thread-3] o.a.n.p.standard.HandleHttpRequest HandleHttpRequest[id=6ceef915-4430-30fa-09d2-b12bb2142172] Failed

How keep the from losing original content when a replacetext is performed for an invokehttp

I have a situation where I need to do a post using an invokehttp for performing a lock operation on another web server. This requires me to do a replacetext in order to add the required json needed for the post. I wanted to do this call before I performed a putfile call on my system but that

SOLVED: NIFI 1.9.2 PutMongo Update An Existing Filed

This turned out to be pilot error because I had the wrong variable int the mongo collection field From: William Gosse Sent: Thursday, August 8, 2019 4:15 PM To: users@nifi.apache.org Subject: RE: NIFI 1.9.2 PutMongo Update An Existing Filed [CAUTION: This email originated from outside

RE: NIFI 1.9.2 PutMongo Update An Existing Filed

I'm trying to get a PutMongo processor to preform an update on an existing field It the processor I have the following settings: Mode: update Upsert: false Update Query: {"resourceId" : ${resourceId}} Update Mode: With operators enabled Before I go into the PutMongo I do a ReplaceText to put my

NIFI 1.9.2 PutMongo Indexes

Is there any way to have Mongo create an index the first time it puts a document into a collection. It creates the database and collection just find if they don't exit. I like to have add indexes as well.

RESOLVED: NIFI 1.9.2 StandardHttpContextMap Request Expiration value setting

Actually I just realized that the settings for the StandardHttpContextMap are in my template so I can set the Request Expiration value there. I have already automated the deployment of my template so the change to value happens when I redeploy. From: William Gosse Sent: Wednesday, May 29

NIFI 1.9.2 StandardHttpContextMap Request Expiration value setting

Is there a way to set the StandardHttpContextMap Request Expiration value other than through the GUI? Can it be set through a configuration file or by the restful API?

RE: 503 Service Unavailable - Jetty Server

This sounds a lot like what I'm experiencing: http://mail-archives.apache.org/mod_mbox/nifi-issues/201808.mbox/%3cjira.13179212.1534379379000.90358.1534379760...@atlassian.jira%3E I don't quite have the volumes but it's the same symptoms. From: William Gosse Sent: Saturday, May 25, 2019 12:22

RE: 503 Service Unavailable - Jetty Server

I should mention that I'm on Nifi 1.9.2 From: William Gosse Sent: Wednesday, May 29, 2019 4:04 PM To: users@nifi.apache.org Subject: RE: 503 Service Unavailable - Jetty Server This sounds a lot like what I'm experiencing: http://mail-archives.apache.org/mod_mbox/nifi-issues/201808.mbox/%3cjira

503 Service Unavailable - Jetty Server

It looks like something went wrong with my http jetty server I think after I restarted NiFi. I began having a 503 error response being generated when I made requests against my HandleHttpRequest processor. I also noticed that I could not properly disable and re-enable the

RE: java.lang.IllegalStateException: AsyncContext completed and/or Request lifecycle recycled ???

May 24, 2019 at 5:59 PM William Gosse mailto:william.go...@aifoundry.com>> wrote: Does anyone know what this exception is about: 2019-05-23 19:09:07,102 ERROR [Timer-Driven Process Thread-2] o.a.n.p.standard.HandleHttpResponse HandleHttpResponse[id=d7b2feb7-4a1e-38c8-07b9-e3d9448bc92b]

java.lang.IllegalStateException: AsyncContext completed and/or Request lifecycle recycled ???

Does anyone know what this exception is about: 2019-05-23 19:09:07,102 ERROR [Timer-Driven Process Thread-2] o.a.n.p.standard.HandleHttpResponse HandleHttpResponse[id=d7b2feb7-4a1e-38c8-07b9-e3d9448bc92b] Failed to complete HTTP Transaction for

RE: NiFi 1.9.1 release contains a bug causing content repos to fill...

reserved=0= On Tue, Apr 2, 2019 at 12:17 PM William Gosse wrote: > > Also can someone explain more what this issue is and how serious it is. > > Can a patch be made available to fix this issue for existing 1.9.1 > installations? > > > > From: Joe Witt >

RE: NiFi 1.9.1 release contains a bug causing content repos to fill...

Also can someone explain more what this issue is and how serious it is. Can a patch be made available to fix this issue for existing 1.9.1 installations? From: Joe Witt mailto:joe.w...@gmail.com>> Sent: Saturday, March 30, 2019 12:32 PM To: users@nifi.apache.org

RE: NiFi 1.9.1 release contains a bug causing content repos to fill...

Can a patch be made available to fix this issue for existing 1.9.1 installations? From: Joe Witt Sent: Saturday, March 30, 2019 12:32 PM To: users@nifi.apache.org Subject: Re: NiFi 1.9.1 release contains a bug causing content repos to fill... [CAUTION: This email originated from outside of

RE: Merge? Notify? Wait?

d, there's no need to fetch the contents of the file until after you've already made the web request and retrieved the client id. Once you have that, you can fetch the contents and then use PutFile. Thanks -Mark On Mar 27, 2019, at 2:25 PM, William Gosse mailto:william.go...@aifoundry.com>>

Merge? Notify? Wait?

I’ve been trying to solve this problem in Nifi for the past couple of days and haven’t been able to find the secret sauce yet. I goes something like this: List/Fetch a file Extract an client name from part of the filename using an UpdateAttribute At this I send the flow in two different

RE: Weird ListFile Issue

you recognize the sender and know the content is safe.] Looks like the processor started listing CWD On Fri, Mar 22, 2019, 2:00 PM William Gosse mailto:william.go...@aifoundry.com>> wrote: The real var name was aimuploaddir and the error was aimduploaddir.

RE: Weird ListFile Issue

depends on many factors such as os behaviors. thanks On Fri, Mar 22, 2019, 12:47 PM William Gosse mailto:william.go...@aifoundry.com>> wrote: I ran into kind of a weird issue with the ListFile processor. I was referencing a variable for my input directory and had enter the variabl

Weird ListFile Issue

I ran into kind of a weird issue with the ListFile processor. I was referencing a variable for my input directory and had enter the variable name incorrectly. So I assumed that the with my incorrect variable name the value of the Input Directory would be null or an empty string. When I

RE: Automate the Enablement of a StandardHttpContextMap

elp it is much approceiated. -Original Message- From: William Gosse Sent: Thursday, March 21, 2019 2:55 PM To: users@nifi.apache.org Subject: RE: Automate the Enablement of a StandardHttpContextMap [CAUTION: This email originated from outside of Kodak Alaris. Do not click links or o

RE: Automate the Enablement of a StandardHttpContextMap

g-enable-services" that can be used to enable all the services in a given process group. You could call this from your script like "./bin/cli.sh nifi pg-enable-service -pgid someid". On Thu, Mar 21, 2019 at 11:29 AM William Gosse wrote: > > I’m trying to automate

Automate the Enablement of a StandardHttpContextMap

I'm trying to automate the deployment of a template that contains a HandleHttpRequest processor. My issue is that this always comes up with an Invalid component marker after a fresh deployment of the template. The cause of this marker is that the StandardHttpContextMap in the HandleHttpRequest

RE: NiFi 1.7.1 remote group not connecting when added through restful api until nifi restarted

takes more than 10 seconds on a 5 nodes cluster. Chris -Original Message----- From: William Gosse Sent: Donnerstag, 15 November 2018 18:03 To: users@nifi.apache.org Subject: RE: NiFi 1.7.1 remote group not connecting when added through restful api until nifi restarted I don't believe I see

RE: NiFi 1.7.1 remote group not connecting when added through restful api until nifi restarted

ection refused? It should not require a NiFi restart to establish connection. Thanks, Koji On Thu, Nov 15, 2018 at 1:38 AM William Gosse wrote: > > I'm using NiFi's restful api to create a process group from a template > that contains a file folder listener and a remote gro

NiFi 1.7.1 remote group not connecting when added through restful api until nifi restarted

I'm using NiFi's restful api to create a process group from a template that contains a file folder listener and a remote group. I also have an existing input port going to a process group that has the file fetch and everything else for processing the file that was fetched. This is not added by

Problem with remote groups reconnecting to input port after restart.

Hi, I'm trying to implement a Listfile>FetchFile pattern similar to the one described on the following link: https://pierrevillard.com/2017/02/23/listfetch-pattern-and-remote-process-group-in-apache-nifi/ I have multiple Listfiles process groups each containing a remote process group that