We're updating the issue view to help you get more done. 

primay key updated more than once in a batch will fail to be applied correctly

Description

it's a very corner case and don't have a good solution so far , probably need to document it.

Release Notes

None

Activity

Show:
Sagar Kapare
4 days ago

please help prioritize this issue since its a corner case.

Albert Shau
3 days ago

How rare this is really depends on the write pattern for the user table – it could potentially be a common scenario and not a corner case.

 

When Sean and I discussed a while back, we couldn’t think of an easy way to handle this. Haven’t thought through this very far, but it may potentially be easier to handle if we write an update as a delete and then an insert in the staging table?

Assignee

Bhooshan Mogal

Reporter

Sean Zhou

Labels

None

Docs Impact

None

UX Impact

None

Components

Priority

Minor
Configure