Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 12 May 2015 18:21:00 +0000 (UTC)
From: "John Vines (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12829266.1431454845000.90495.1431454860703@Atlassian.JIRA>
In-Reply-To: <JIRA.12829266.1431454845000@Atlassian.JIRA>
References: <JIRA.12829266.1431454845000@Atlassian.JIRA>
 <JIRA.12829266.1431454845277@arcas>
Subject: [jira] [Created] (ACCUMULO-3805) No means to monitor/interact with
 FATE programmatically
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

John Vines created ACCUMULO-3805:
------------------------------------

             Summary: No means to monitor/interact with FATE programmatically
                 Key: ACCUMULO-3805
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3805
             Project: Accumulo
          Issue Type: Bug
          Components: fate
            Reporter: John Vines


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.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)