I have had this issue in NiPyAPI when the local system does not have a timezone set, or at least setting tz_data resolved it in the docker images I was building. This was in my python client, not Java however, so I am unsure if that would affect things.
On Tue, Mar 17, 2020 at 8:04 PM alec_osborne <[email protected]> wrote: > Hi, > > When using > > "ProcessGroupsApi.submitUpdateVariableRegistryRequest(ID,VariableRegistryEntity)", > the response of Nifi can't be parsed. > > In detail, the returned Data-Format '03/17/2020 12:59:47.087 CET' can not > be > parsed by the java.time.DateTimeFormatter. Following Exception is thrown: > > java.time.format.DateTimeParseException: Text '03/17/2020 12:59:47.087 CET' > could not be parsed at index 0 > > The corresponding Formatter seems to expect a string in the following > format: '2011-12-03T10:15:30+01:00' as it is created in JSON.java with the > following statement: > > JSON.java: > Line152:DateTimeFormatter.ISO_OFFSET_DATE_TIME > > Use anybody the same API Request and have the same problem? > > Thanks > > Alec. > > > > -- > Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/ >
