Uploaded image for project: 'Phoenix Omid'
  1. Phoenix Omid
  2. OMID-82 Integrating Omid with Phoenix
  3. OMID-113

Set conflict free option when constructing TTable

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.0.0
    • 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.

      Attachments

        1. OMID-113_v2.patch
          19 kB
          James R. Taylor

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            jamestaylor James R. Taylor
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment