-
Bug
-
Resolution: Fixed
-
Normal
-
None
-
None
-
None
-
None
Example Query:
- XML: https://beta.musicbrainz.org/ws/2/release-group/?query=rgid:b0d0fc64-11f8-36d3-89bc-e4327c5a6fba
- JSON: https://beta.musicbrainz.org/ws/2/release-group/?query=rgid:b0d0fc64-11f8-36d3-89bc-e4327c5a6fba&fmt=json
- JSON (lookup): https://beta.musicbrainz.org/ws/2/release-group/b0d0fc64-11f8-36d3-89bc-e4327c5a6fba?fmt=json&inc=releases
The XML version looks fine at first glance.
However, the JSON version has issues.
- There is a spurious 'count' field in the release group.
This seems to come from the list of releases (in a lookup including releases, this field is not deserialized at all) - The 'primary-type-id' field is missing
- The 'secondary-type-ids' field is missing
- A spurious 'type-id' field is present
This seems to contain the first secondary type id if one is set, or the primary type id if not.
Either way, information is definitely lost here.
This is not a case of the data not having been retained in the index - the XML result includes all type ids correctly.
- depends on
-
SEARCH-628 'primary-type-id' field is missing from JSON release group search results
- Closed
-
SEARCH-629 'secondary-type-ids' field is missing from JSON release group search results
- Closed
- has related issue
-
SEARCH-627 Remove spurious 'count' from JSON release group search results
- Open
-
SEARCH-630 Remove old 'type' and 'type-id' from release group search results
- Reopened