Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1136
NiFi follows the semantic versioning guidelines. What your suggesting is
changing the meaning of those fields. They are strings that are meant to be
human-readable (one with the time and the other with the date and time). If we
change them, we could be affecting any existing clients of that API that expect
them to be human-readable strings. The clients I'm referring is anyone
consuming this API in an existing version of NiFi. As you mentioned, in our
case we would need to update the UI (which is a client of this API) to reformat
it as necessary. This is not something we would expect others to do in a
minor/incremental version change or without somehow versioning the API.
As I mentioned earlier, I believe that any field using a JAXB adapter is
currently being interpreted incorrectly by Swagger. While it would be nice if
Swagger could correctly determine the actual data type (a string in this case
and not a date-time) it appears they at least provide a mechanism for setting
it explicitly. We should be taking advantage of that.
---
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.
---
