Available SQL fn in QueryRecord??

Hello, Is there a list or somewhere we can find all the available SQL functions available in QueryRecord? Regards Dano

Re: [EXT] ReplaceText cannot consume messages if Regex does not match

Patch available at https://issues.apache.org/jira/browse/NIFI-5761 On Thu, 18 Oct 2018 at 13:33 Juan Pablo Gardella < gardellajuanpa...@gmail.com> wrote:

Re: [EXT] Re: Cluster Warnings

Karthik, It is really difficult to debug via snippets of logs for a case like this. I'm not quite sure what to say. NiFi 1.8.0 download is available now or will be within 24 hours. You might want to try that and see if it improves this case. Otherwise, it will be necessary to see a more

RE: [EXT] Re: Cluster Warnings

Any light on this? We’re still seeing warnings every 10 seconds which is really annoying and no idea what’s triggering them. -Karthik From: Karthik Kothareddy (karthikk) [CONT - Type 2] Sent: Tuesday, October 16, 2018 8:27 AM To: users@nifi.apache.org Subject: RE: [EXT] Re: Cluster Warnings

Re: ScriptedRecordReader Error Handling

As a backup to that, you can also write a Groovy script for ExecuteScript that uses stax to iterate over the XML data. It won't care about schemas (Avro or XML) and stuff like that; just check for basic validity. On Fri, Oct 26, 2018 at 11:42 AM Joe Witt wrote: > Cant your logic detect the

Re: ScriptedRecordReader Error Handling

Cant your logic detect the strange characters and then apply its behavior? Alternatively, you could perhaps use ValidateRecord and have its reader only understand the good records. It should kick out the bad records and you can then apply deeper processing on them. Thanks On Fri, Oct 26, 2018

ScriptedRecordReader Error Handling

Is there anyway for a ScriptedRecordReader to set an attribute on a FlowFile when there is an error? Have a situation where I've written a groovy script to parse xml into a specific record structure and occasionally the incoming data has characters not allowed in XML. Unfortunately the system

Re: DBCPConnectionPool Not looking up

Thanks Alexandre, This took us some time to figure out but the culprit turned out to be a merge processor that didn't merge properly, which is another problem for another time :) Martijn On Fri, 26 Oct 2018, at 05:06, Cardinal, Alexandre wrote: > Hey Martijn, > > I had this exact issue