James Taylor created OMID-113: --------------------------------- Summary: Set conflict free option when constructing TTable Key: OMID-113 URL: https://issues.apache.org/jira/browse/OMID-113 Project: Apache Omid Issue Type: Sub-task Reporter: James Taylor
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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)