[
https://issues.apache.org/jira/browse/NIFIREG-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16212143#comment-16212143
]
ASF GitHub Bot commented on NIFIREG-36:
---------------------------------------
Github user kevdoran commented on the issue:
https://github.com/apache/nifi-registry/pull/23
This is now rebased against the branch that adds integration tests. We
should wait to merge this until that branch is finalized and merged to master
so this can be rebased again if needed, but let me know what you think of the
changes in the last commit on this branch.
I added a couple other changes to this as well, including:
- a custom object mapper in the client
- mapper providers are now loaded via package scanning in
NiFiRegistryResourceConfig (possible by also adding Spring @Component
annotations)
> Add Jackson JsonInclude Annotations to NiFi Registry Data Model classes
> -----------------------------------------------------------------------
>
> Key: NIFIREG-36
> URL: https://issues.apache.org/jira/browse/NIFIREG-36
> Project: NiFi Registry
> Issue Type: Improvement
> Reporter: Kevin Doran
> Assignee: Kevin Doran
> Fix For: 0.0.1
>
>
> Currently, NiFi Registry responses include null values for optional fields in
> the serialized Json. This ticket is to add Jackson annotations that prevent
> explicit "null" from being serialized for optional fields, instead just
> omitting the optional fields, as not all clients/frameworks can interpret
> null correctly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
