TFD
ThoughtSpot For Developers•5d ago
euporphium

euporphium - Hey all,Reference: https://disco...

Hey all, Reference: https://discord.com/channels/1143209406037758065/1143209464875462756/1441070770435526718 We're working to add/remove user favorites via the endpoint: POST /api/rest/2.0/users/{user_identifier}/update When multiple updates happen close together, we're seeing the following error response: 
{
   "error":{
      "message":{
         "debug":{
            "code":14009,
            "incident_id_guid":"<>",
            "trace_id_guid":"tracing-disabled",
            "debug":"[\"Error Code: FAILED_TO_COMMIT Incident Id: <>\\nError Message: com.thoughtspot.atlas.AtlasException:  code\\u003dVERSION_CONFLICT, Node Content updated before put\\<>\"]"
         }
      }
   }
}
{
   "error":{
      "message":{
         "debug":{
            "code":14009,
            "incident_id_guid":"<>",
            "trace_id_guid":"tracing-disabled",
            "debug":"[\"Error Code: FAILED_TO_COMMIT Incident Id: <>\\nError Message: com.thoughtspot.atlas.AtlasException:  code\\u003dVERSION_CONFLICT, Node Content updated before put\\<>\"]"
         }
      }
   }
}
A couple of questions: 1. Are we only able to update favorites sequentially for a user (one update at a time)? 2. Is there a supported way to handle or avoid these VERSION_CONFLICT errors when updates happen in quick succession? Thanks!
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?