Re: DBCPConnectionPoolLookup

Awesome I'll try it next week and if I can get it to work I'll let you know Thx !!! On Fri, Oct 4, 2019, 6:24 PM Peter Turcsanyi wrote: > Hi John, > > You need to add dynamic properties to DBCPConnectionPoolLookup controller > service. The name of the property corresponds to database.name

Re: Which JAR can I find org.apache.nifi.record.path.*

Eric, I have, specifically for the unit tests. You can find the scaffolding at [1] and the actual script at [2] (it's trivial but should have all the boilerplate). Also it may interest you to know that I have put up a Pull Request for the nifi-record-path addition to the scripting bundle [3] :)

Re: DBCPConnectionPoolLookup

Hi John, You need to add dynamic properties to DBCPConnectionPoolLookup controller service. The name of the property corresponds to database.name attribute, the value is the DBCPConnectionPool that can be looked up (by the name of the property). So the attribute database.name ties back to the

Re: Which JAR can I find org.apache.nifi.record.path.*

Hi Matt, thanks for letting me know. Have you ever wrote a ScriptedRecordSetWriter? I couldn't find any example of it. Do you have any to share? Best regards, Em sex, 4 de out de 2019 às 18:00, Matt Burgess escreveu: > Eric, > > The RecordPath classes are in the nifi-record-path JAR, which is

H2 DB locking error - Timeout trying to lock table "ACTION"

Hi Folks, We recently encountered an error on a prod cluster where Nifi couldn't acquire an H2 database lock when the canvas UI was modified, 'Timeout trying to lock table "ACTION"'. I wasn't able to track down who held the lock, or even where the lock was at. Ended up restarting the cluster,

Re: Which JAR can I find org.apache.nifi.record.path.*

Eric, The RecordPath classes are in the nifi-record-path JAR, which is not currently included in the scripting bundle. I have written up an improvement Jira [1] to add this. Regards, Matt [1] https://issues.apache.org/jira/browse/NIFI-6741 On Fri, Oct 4, 2019 at 3:30 PM Eric Chaves wrote: > >

Re: HandleHTTPRequest 503 error issue

Yes, thanks. Is there an ETA for 1.10? On Fri, Oct 4, 2019 at 3:05 PM Peter Turcsanyi wrote: > Hi Wyllys, > > It has been fixed in NIFI-6317 > which will be shipped > in the upcoming 1.10 release. > Could you please retest your workload on that

DBCPConnectionPoolLookup

Does someone have a basic example of using this ? I really dont understand it. And it seems useful. Does the attribute database.name tie back to the "Name" of the DBCPConnectionPool ? How do you pass that dynamically ? Via some updateattibute processor ? Be great to see a very basic flow on

RE: HandleHTTPRequest 503 error issue

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

Which JAR can I find org.apache.nifi.record.path.*

Hi folks, I'd like to use the Record Path classes in a groovy script for a InvokeScriptedProcessor but when I import those classes they aren't found. Can anyone point me the JAR where they reside? The classes I'm importing are import org.apache.nifi.record.path.FieldValue import

Re: HandleHTTPRequest 503 error issue

Hi Wyllys, It has been fixed in NIFI-6317 which will be shipped in the upcoming 1.10 release. Could you please retest your workload on that version when it is available? Regards, Peter Turcsanyi On Fri, Oct 4, 2019 at 6:28 PM Wyllys Ingersoll <

HandleHTTPRequest 503 error issue

I believe this issue: https://issues.apache.org/jira/browse/NIFI-5522 is a regression in Nifi 1.9.2, it was marked as fixed in 1.8.0, but Im seeing it a lot in 1.9.2 I can recreate it fairly regularly when I am hitting the endpoint pretty heavily and an error is encountered. The process return