RE: NiFi ExecuteSQL error => can not be represented as java.sql.Timestamp

Hi Koji, I was able to fix this issue using following with my JDBC connection - jdbc:mysql://localhost:3306/nifi_test?zeroDateTimeBehavior=convertToNull It was basically causing due to null values in a Timestamp column which I was able to cater by converting it to null. Thanks, Mohit

RE: [EXT] Re: Metrics on Lineage Duration

Thanks Pierre, though I think you meant to send me: https://pierrevillard.com/2017/05/15/monitoring-nifi-workflow-sla/, which was much more helpful ☺. From: Pierre Villard [mailto:pierre.villard...@gmail.com] Sent: Tuesday, November 07, 2017 8:35 PM To: users@nifi.apache.org Subject: [EXT] Re:

RE: [EXT] Re: Metrics on Lineage Duration

Mark, While Pierre’s solution will probably be more helpful in the long run, this provides an easy way for me to examine the data by hand right now. I didn’t know that metric was on the Status History window, good to now! Thanks, Peter From: Mark Payne [mailto:marka...@hotmail.com] Sent:

Re: NiFi ExecuteSQL error => can not be represented as java.sql.Timestamp

Hi Mohit, The exception looks as if the entire string ' 821725069 2161514622096 ... 0-00 0 3' was converted to java.sql.Timestamp. Would you share your create table DDL statement, few sample record data, NiFi, MySQL and JDBC driver version you're using? Thanks, Koji On

Incorrect PublishKafka_0_10 documentation?

I've been struggling to get NiFi working with Kerberos authenticated Kafka. According to the docs, the "Kerberos Service Name" property specifies: "The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config. Corresponds to Kafka's

NiFi ExecuteSQL error => can not be represented as java.sql.Timestamp

Hi all, I'm facing issue while fetching records from mysql table with Timestamp column. Table has 4 timestamp columns. It is working fine when I change the data type to string. It throws the following exception : org.apache.nifi.processor.exception.ProcessException:

RE: [EXT] Re: Polling Processors impact on Latency

Chirag, Peter's note about bored yield duration is right on. Some additional things I'd like to point out are: 1) You might get the lowest latency in a configuration where the processor runs continuously (bored yield duration 0). This is because with the code executing continuously, CPU

Re: Metrics on Lineage Duration

Peter, In the UI you can right-click on a Processor and go to "View Status History" to see a chart of different metrics over time. One of those metrics is the Average Lineage Duration (averaged over a 5-minute period). Of course, you are asking for a reporting task/processor that does this.

Re: Metrics on Lineage Duration

Hi Peter, There is not as far as I know. What I usually do is to use ExecuteScript processor to extract the lineage duration of the flow file into an attribute of the flow file where I feel this information is useful for my workflow and I send it to whatever monitoring destination I have. This

RE: [EXT] Re: Polling Processors impact on Latency

If you schedule the processor to run every 0 sec (the default) then in my experience you won’t notice latency from polling at all. But I guess this depends on your expectations, volume, and over all Flow processing time. Yes, event driven may help, but from what I’ve read it’s more about

Re: Polling Processors impact on Latency

Thanks Andrew for the quick response. I am more concerned about the processors polling for flow files on the connection between the processors? Thanks, Chirag Sent from Yahoo Mail on Android On Tue, 7 Nov 2017 at 5:24 PM, Andrew Grande wrote: Yes, polling increases

Metrics on Lineage Duration

Is there a reporting task/processor that will let me aggregate Lineage Duration's for a point in time so I can monitor my flow using this metric? Thanks, Peter

Re: Polling Processors impact on Latency

Yes, polling increases latency in some cases. But no, NiFi is not just polling. It has all kinds of sources, and listening vs polling vs subscribing purely depends on the protocol of that given processor. Hope this helps, Andrew On Tue, Nov 7, 2017, 1:39 AM Chirag Dewan

Re: SplitAvro fails to split data

Hi Koji,Thank you for testing my problem with NiFi 1.4 and verifying that it works. It is good to know that once we upgrade our NiFi infrastructure, the problem would go away. Thanks,Pradip On Tuesday, November 7, 2017, 1:14:11 AM MST, Koji Kawamura wrote: Hi

Re: SplitAvro fails to split data

Hi Pradip, When I tested the scenario with NiFi 1.4, SplitAvro created an outgoing FlowFile containing single record as expected when the incoming FlowFile only has one Avro record. In SplitAvro change histories, I found NIFI-2841. I assume the change fixed the split behavior with single input