[GitHub] nifi issue #869: NIFI-2576 - PutSQL assumes all Timestamps are provided in E...

2016-08-16 Thread bbende
Github user bbende commented on the issue: https://github.com/apache/nifi/pull/869 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

[GitHub] nifi issue #869: NIFI-2576 - PutSQL assumes all Timestamps are provided in E...

2016-08-15 Thread patricker
Github user patricker commented on the issue: https://github.com/apache/nifi/pull/869 I can go for that. Updated. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and

[GitHub] nifi issue #869: NIFI-2576 - PutSQL assumes all Timestamps are provided in E...

2016-08-15 Thread bbende
Github user bbende commented on the issue: https://github.com/apache/nifi/pull/869 @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,