Site-to-site not working

Hello, I have used Nifi for a while on my laptop. Now I wanted to setup a second machine communicating with the first one - either using Nifi oder Minifi. For the moment I have Nifi 1.0.0 running on both and I followed the instructions of how to setup Nifi. I read documentation, but there must

Re: Site-to-site not working

The socket host should be the ip of the machine it is on, not the machine that it expects to receive the data from. That variable is similar to the httphost or https host variable, also in the prop file. Hope that helps! Sent from my iPhone > On Sep 10, 2016, at 6:02 AM, Uwe Geercken wrote:

Aw: Re: Site-to-site not working

Thank you so much Corey - that did it. Finally I can do more interesting things. Have a nice weekend. Uwe > Gesendet: Samstag, 10. September 2016 um 14:09 Uhr > Von: "Corey Flowers" > An: dev@nifi.apache.org > Betreff: Re: Site-to-site not working > > The socket host should be the ip of the ma

RE: Re: Re: PutSQL error sql.arg3.value cannot convert to timestamp

I use PutFile following ConvertAvroToJSON to check the content of ConvertAvroToJSON's output. From: Li, Peng Sent: Saturday, 10. September 2016 16:00 To: 'dev@nifi.apache.org' Subject: Re: Re: PutSQL error sql.arg3.value cannot convert to timestamp Hi Bryan, In provenance the attribute sql.arg

Re: Re: PutSQL error sql.arg3.value cannot convert to timestamp

Hi Bryan, In provenance the attribute sql.args.3.value was given as "2016-04" and sql.args.3.type was given as "93". But as already said in previous mail, i checked the content of the output of ConvertAvroToJSON and "2016-04-29 00:00:00.0" was given there, so I think this value was given to th

Re: Nifi Debugging AWS PutS3 processor

Julie, Generally, you *shouldn't* need to set the endpoint if you are using standard AWS services, but there should be no harm in setting it consistent with the region you are trying to access. The S3 endpoints follow a scheme of

Re: Re: PutSQL error sql.arg3.value cannot convert to timestamp

Peng, Thanks for checking what the value for sql.args.3.value was... the fact that it is already truncated there and not including the hours/mins/seconds means something is going wrong before it even gets to PutSQL. I was looking at the code in ConvertJsonToSQL and found this code: final Integer

Re: Re: PutSQL error sql.arg3.value cannot convert to timestamp

I think we're running into NIFI-2625 [1] and/or NIFI-1613 [2], the column size returned is for the underlying data type, not the String literal it corresponds to. Regards, Matt [1] https://issues.apache.org/jira/browse/NIFI-2625 [2] https://issues.apache.org/jira/browse/NIFI-1613 On Sat, Sep 10,

Re: Re: PutSQL error sql.arg3.value cannot convert to timestamp

Good find Matt, from a quick glance it looks like NIFI-2625 is definitely related, although it is more specific to when the timestamp is in milliseconds vs. nano-seconds. Part of the problem is that PutSQL can handle the epoch OR a date string, but the Avro produced by ExecuteSQL/QueryDatabaseTabl

RE: Re: PutSQL error sql.arg3.value cannot convert to timestamp

Bryan/Matt, Wouldn't a JDBC truncation blacklist be easiest? If the destination type is timestamp/any other applicables, then don't take the substring? --Peter -Original Message- From: Bryan Bende [mailto:bbe...@gmail.com] Sent: Saturday, September 10, 2016 1:00 PM To: dev@nifi.apache.

Re: PutSQL error sql.arg3.value cannot convert to timestamp

I think Toivo had some thoughts on this, but IIRC the basic idea is not to use getColumnWidth when it doesn't align with literals. Either convert and trim or skip the trim I think? > On Sep 10, 2016, at 10:38 PM, Peter Wicks (pwicks) wrote: > > Bryan/Matt, > > Wouldn't a JDBC truncation blac