[ 
https://issues.apache.org/jira/browse/HDDS-15096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Sarin updated HDDS-15096:
------------------------------
    Description: 
Recon exposes JSON under /api/v1 via Jersey and jersey-media-json-jackson 
(JacksonJaxbJsonProvider). Several API types in 
org.apache.hadoop.ozone.recon.api.types use JAXB @XmlElement names that do not 
match plain JavaBean JSON names (e.g. KeyMetadata Volume vs volume, 
DatanodeMetadata opState vs operationalState, ContainerMetadata ContainerID vs 
containerID). Existing endpoint tests often assert Response#getEntity() as Java 
objects and never validate serialized JSON, so a Jersey/Jackson upgrade or 
provider misconfiguration can rename JSON fields without failing unit tests 
breaking the Recon UI and API consumers.

 

  was:
Recon exposes JSON under /api/v1 via Jersey and jersey-media-json-jackson 
(JacksonJaxbJsonProvider). Several API types in 
org.apache.hadoop.ozone.recon.api.types use JAXB @XmlElement names that do not 
match plain JavaBean JSON names (e.g. KeyMetadata Volume vs volume, 
DatanodeMetadata opState vs operationalState, ContainerMetadata ContainerID vs 
containerID). Existing endpoint tests often assert Response#getEntity() as Java 
objects and never validate serialized JSON, so a Jersey/Jackson upgrade or 
provider misconfiguration can rename JSON fields without failing unit 
tests—breaking the Recon UI and API consumers.

 


> [Recon] Add JSON wire-format contract tests for JAXB-annotated API types
> ------------------------------------------------------------------------
>
>                 Key: HDDS-15096
>                 URL: https://issues.apache.org/jira/browse/HDDS-15096
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: Ozone Recon
>            Reporter: Arun Sarin
>            Assignee: Arun Sarin
>            Priority: Major
>
> Recon exposes JSON under /api/v1 via Jersey and jersey-media-json-jackson 
> (JacksonJaxbJsonProvider). Several API types in 
> org.apache.hadoop.ozone.recon.api.types use JAXB @XmlElement names that do 
> not match plain JavaBean JSON names (e.g. KeyMetadata Volume vs volume, 
> DatanodeMetadata opState vs operationalState, ContainerMetadata ContainerID 
> vs containerID). Existing endpoint tests often assert Response#getEntity() as 
> Java objects and never validate serialized JSON, so a Jersey/Jackson upgrade 
> or provider misconfiguration can rename JSON fields without failing unit 
> tests breaking the Recon UI and API consumers.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to