[
https://issues.apache.org/jira/browse/ACCUMULO-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-3805.
-----------------------------------------
Resolution: Not A Problem
The admin command can do some of these things. If this is still a problem,
please create a new issue or PR at https://github.com/apache/accumulo
> 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
> Priority: Major
>
> 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
(v8.20.10#820010)
