[jira] [Resolved] (KUDU-619) Consolidate, clean up, and bring consistency to tools

["Adar Dembo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adar Dembo resolved KUDU-619.
-----------------------------
       Resolution: Fixed
         Assignee: Adar Dembo
    Fix Version/s: 1.0.0

Dinesh and I fixed this in a series of commits. There's now just a single command line tool called 'kudu'.

> Consolidate, clean up, and bring consistency to tools
> -----------------------------------------------------
>
>                 Key: KUDU-619
>                 URL: https://issues.apache.org/jira/browse/KUDU-619
>             Project: Kudu
>          Issue Type: Improvement
>          Components: ops-tooling
>    Affects Versions: M5
>            Reporter: Adar Dembo
>            Assignee: Adar Dembo
>             Fix For: 1.0.0
>
>
> 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:
> # Consolidate all tools that handle the same use case, possibly removing any duplicated tools.
> # Give all tools a consistent naming scheme.
> # Ensure that all tools are consistent w.r.t. gflags usage, output style, logging, and other expectations.



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