Hierarchy read API of collections in edit mode is failing with server error #19
Replies: 3 comments 13 replies
-
@amitpriyadarshi i have also noticed the same issue |
Beta Was this translation helpful? Give feedback.
-
@kameshbhr & @anandvarada - This is happening only when Org Admin opens collections published by others from the 'All textbooks' tab. @amitpriyadarshi can correct the data for the impacted textbooks to unblock users. |
Beta Was this translation helpful? Give feedback.
-
RCA: When the content-update (v3) API is invoked on a published collection, "relational_metadata" column in the cassandra is getting insert with null as string data for the newly created image node. |
Beta Was this translation helpful? Give feedback.
-
@Krishnaj20 @vinukumar-vs @AmiableAnil
Collection hierarchy read api is failing with server error with below response:
Analysis:
There is an external property named
relational_metadata
introduced inrelease-4.7.0
against the collection objects. If this property isnull
for aLive
collection object and we call update hierarchy API, its draft version gets created in neo4j and the external property gets inserted into Cassandra against the draft object. In this case, therelational_metadata
field gets set as"null"
as a string (instead ofnull
).Because of which hierarchy read API throws an exception while parsing this value to object and throws Server Exception in response.
There are about 780 draft versions of collections that are impacted by this issue. This is impacting many users to update the already published collection.
Beta Was this translation helpful? Give feedback.
All reactions