NIFI-2576 - PutSQL assumes all Timestamps are provided in Epoch

[patricker]

This change allows for either epoch timestamps or "yyyy-MM-dd hh:mm:ss.SSS" format; which is the format you get when you call ResultSet.getString on a JDBC Timestamp column.

Also include a unit test for PutSQL to test both flavors of Timestamps.

[bbende]

@patricker thanks for the contribution! Definitely makes sense to support both formats...

What do you think about using a regex to determine if it is a long, and if so then parseLong, otherwise attempt to parse a date? (could be the other way around, but I was thinking the regex for a long is easiest)

I'm thinking of the case where someone is always sending in longs and it is continuously throwing/catching the parse exception, that may end up being expensive.

[patricker]

@bbende I can go for that. Updated.

[bbende]

Thanks for update, merged to master!

Just an FYI, I had a bit of trouble getting the changes to apply from the PR onto master... for future it would be easiest to have a specific branch with only one commit for the initial PR, rather than submitting from your master to NiFi master. Thanks again.