Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1136
@mike42 - Thanks for checking out Apache NiFi and looking to make
improvements here. We just released version 1.0.0 so we don't have another
major release scheduled in the immediate future. We could certainly look to
update the endpoints to return these new values in addition to the existing
ones (which could then be marked as deprecated). Or we could investigate a
means for versioning the API so that existing clients wouldn't break and new
clients could utilize the new endpoints. Though it may make sense to do this
work when we add i18n support throughout the application which will likely
require either a major NiFi version change or supporting multiple versions of
the REST API concurrently.
Regardless what additional work we identify here, I believe the work that
was discussed with @simplesteph needs to happen as the documentation is
currently misreporting the actual data type of these fields.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
