obiwanzenobiOriginal post
Rank 3: Container
no - everything is ok with my relationships - here is data
JSON
{ "name":"Współczesność – o epoce", "onlyForPremium":false, "isMediaPremiumOnly":false, "mainMedia":"https://vimeo.com/855166568", "mediaType":"video", "mediaSource":"vimeo", "mediaThumbnail":"64f5c6fef098d9d485d8", "mediaContent":"64f5c6ff0ce0bb1785b0", "slug":null, "createdBy":null, "createdById":null, "updatedBy":null, "updatedById":null, "oldTitle":null, "oldAuthor":null, "oldCategory":null, "preview":"word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word word", "metaTitle":null, "metaDescription":null, "metaKeywords":null, "zdayId":"29005", "content":[ ], "contentIds":null, "oldId":null, "assignedToCategories":[ "64f79cced50f0fee7825" ], "search_name_zdayId":"Współczesność – o epoce 29005"}Summary
A user was trying to create a document with a unique ID and no unique indexes but encountered the error "document_already_exists." They discovered that the error was caused by a one-to-one relationship between the documents. The solution was to remove the relationship or add a unique index. However, the user suggested that there should be an error log to identify which unique parameter is causing the failure.