EdColeman
EdColeman
The threads or methods used in the high level use cases I mentioned would be the items to instrument with metrics so that info could be derived in production. (Well,...
If any of these are marked experimental, then I think we should not be enabling them by default. Would providing an "experimental" config, along side (or enabled from) the standard...
Operators are familiar with the current shell fate operations and may be using them more that expected. I'm not opposed to moving it to the admin command, but the same...
I guess I used it because it was available and used it when testing the command line - it looks like without it there is a missing config issue that...
The newlines in the FateSummaryReport were specifically included to visually break up the sections to make it easier for an operator to visually scan and pull out relevant information.
There is a section in the docs (fate.md) that will need to be updated when these changes are merged.
I am not sure that we should have two versions of the same command that use separate options in this release. The current command should be deprecated, but could still...
Would something like ``` fate -list --all or fate -list tx1 tx2 .... ``` work? And pick either list or print?
Yes - I would like cancel and summary to be available - or have a strong pointer to the admin command.
I think it would be enough it if was. ``` fate -cancel 3cb69aefefe6b6d0 2022-09-20T14:18:48,053 [shell.Shell] WARN : WARNING: This command is deprecated for removal. Use 'accumulo admin' This option in...