We have a GeoServer 2.18.2 instance serving data from PostGIS that seems to return a different structure for DescribeFeatureType requests depending on the outputFormat specified in the request.
One of our database tables which is published via GeoServer has 7 column names: [id, geom, code, name, enw, inset_no, category], nothing out of the ordinary. Making a WFS DescribeFeatureType to GeoServer for this and including
outputFormat=application/json provides a complete description of the feature including all of the above attributes from the underlying table. However, if outputFormat is omitted so that GeoServer returns a GML3.2 response, then the name attribute is completely missing from the result.
There are no errors in the log from GeoServer when making these requests and any GetFeature requests against the same data source include the name attribute as expected. It is only DescribeFeatureType requests that seem to be affected, which causes a problem for some clients such as QGIS that use a DescribeFeatureType call to set up a layer. Prefixing the database column and reloading the feature type in GeoServer makes the attribute appear in responses but this feels like a workaround.
Is this expected behaviour from GeoServer or am I seeing a bug?