Github user yjhyjhyjh0 commented on the issue:
https://github.com/apache/nifi/pull/2082
Thanks for the detail explanation.
Indeed using local time zone is more reasonable.
Didnât notice the date will be transform into local time zone once with
value format.
Just want to point out that I first try the approach you mentioned (use
local time zone) will encounter problem with Time type.
My time zone is UTC+8, which cause time string â01:01:01â in Time type
will become negative long value.
This reasonable because Time type only consider time without epoch so it
will be negative if itâs earlier than â08:00:00â.
However this will not pass the LONG_PATTERN in PutSQL and thus consider a
negative long value to be in format "HH:mm:ss.SSSâ instead of long.
This will encounter error while parsing for sure :
java.text.ParseException: Unparseable date: â-28739000â.
If I try your commit with changing the timeStr to â01:01:01" in
testUsingDateTimeValuesWithFormatAttribute will encounter negative long parsing
problem which mentioned above.
Donât know if you will encounter similar problem with **negative long
value in Time type**, too?
I've try your commit together with LONG_PATTERN that also match negative
long value ("^-?\\d{1,19}$â) today and everything works fine now.
Thanks for any response.
---
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 wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
