Uploaded image for project: 'Accumulo'
  1. Accumulo
  2. ACCUMULO-3805

No means to monitor/interact with FATE programmatically

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: fate
    • Labels:
      None

      Description

      With FATE, we have the ability to have strong tracking of operations. However, we hide a lot of this from the client. We have admin utilities plumbed into the shell (FateCommand), but they're not actual APIs. This means there is no API available for failing/deleting/listing fate operations, but it also means there no way to be aware of the txid for a fate operation. This is critical for instances where a potentially distributed client wants to perform a FATEd operation.

      In an ideal world, client would be able to pre-seed the transaction, as we do now, and then issue the command with that id. This would allow the client to be aware of the transaction before it's started so it could be shared.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                vines John Vines
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated: