Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-619

Consolidate, clean up, and bring consistency to tools

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • M5
    • 1.0.0
    • ops-tooling
    • None

    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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            adar Adar Dembo
            adar Adar Dembo
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment