Oleg,
A unix epoch timestamp is explicitly defined as the number of seconds (or
millis) since Jan 1 1970 *UTC*, not any local timezone. Here's an example
ruby expression from both systems correctly returning the 1487804483000
value despite their timezone settings:
irb(main):003:0> Time.parse('2017-02-22T23:01:23Z').to_i*1000
=> 1487804483000
and
2.1.5 :005 > Time.parse('2017-02-22T23:01:23Z').to_i*1000
=> 1487804483000
The value 1487804483000 is the correct millis for the sample value, so I
think the question is whether there is a bug in NiFi or whether the
expression used to parse the date is wrong.
See also:
http://stackoverflow.com/questions/2853977/unix-timestamp-always-in-gmt
https://en.wikipedia.org/wiki/Unix_time
