[
https://issues.apache.org/jira/browse/NIFI-13972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896038#comment-17896038
]
David Handermann commented on NIFI-13972:
-----------------------------------------
Thanks [~turcsanyip]. I created a separate issue NIFI-13978 and submitted a
pull request with proposed changes.
After initial evaluation, the parseUnresolved method approach did not prove to
be sufficient, as the object resolution process involves more steps within the
DateTimeFormatter.
Instead of that approach, I implemented a custom TemporalQuery that looks for
the presence of a ZoneId in the parsed TemporalAccessor. Using this
TemporalQuery avoids the try-catch loop of parseBest() and enables resolution
based on the ZonedDateTime or LocalDateTime as appropriate to the parsed set of
fields.
Glad to compare approaches with that background.
> ObjectLocalDateTimeFieldConverter.convertField ignores time zone
> ----------------------------------------------------------------
>
> Key: NIFI-13972
> URL: https://issues.apache.org/jira/browse/NIFI-13972
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Tamas Palfy
> Assignee: Tamas Palfy
> Priority: Major
>
> When the incoming value is a string that contains timezone/offset information
> the returned LocalDateTime simply ignores that part and returns a value as if
> it was in the local timezone.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
