[KUDU-619] Consolidate, clean up, and bring consistency to tools

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: M5
• Fix Version/s: 1.0.0
• Component/s: ops-tooling
• Target Version/s: Backlog
• Assignee: Adar Dembo
• Reporter: Adar Dembo
• Created: 18/Feb/15 15:41
• Updated: 13/Sep/16 02:43
• Resolved: 13/Sep/16 02:43

Description

We have a number of different tools for working with Kudu data. This is obviously a good thing, but because they were written at different times and by different people, they can be rather inconsistent with one another. Here's the comprehensive list, at the time of writing:

• cfile-dump
• kudu-fs_dump
• kudu-fs_list
• kudu-ksck
• kudu-pbc-dump
• kudu-ts-cli
• log-dump

Let's do a few things to make these tools ready for primetime:

1. Consolidate all tools that handle the same use case, possibly removing any duplicated tools.
2. Give all tools a consistent naming scheme.
3. Ensure that all tools are consistent w.r.t. gflags usage, output style, logging, and other expectations.

Issue Links

• duplicates: KUDU-1574 Bring all the toolsets under new CLI framework
• is duplicated by: KUDU-1041 Rename log-dump to kudu-log-dump