Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Both Delete and Put mutations need to be able to be marked as conflict free. There no need to have an attribute store this information as it's only used on the client to determine which list in Transaction to put the mutation in. By having it as an attribute, you're only bloating the payload of the RPC. Instead, we can pass through in the TTable constructor whether it's a conflict free table or not.