3 replies

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

Hey all,

Reference: dev-help

We're working to add/remove user favorites via the endpoint:

POST /api/rest/2.0/users/{user_identifier}/update

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

VERSION_CONFLICT

errors when updates happen in quick succession?

Thanks!

TFD

ThoughtSpot For Developers•3mo ago•

3 replies

euporphium

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

Hey all,

Reference: dev-help

We're working to add/remove user favorites via the endpoint:

POST /api/rest/2.0/users/{user_identifier}/update

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

VERSION_CONFLICT

errors when updates happen in quick succession?

Thanks!

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

Similar Threads

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

Similar Threads

Similar Threads

Similar Threads