Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-8600

Refactor stress options to reduce prominence of legacy modes (counter_read, etc.)

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Low
    • Resolution: Unresolved
    • None
    • Legacy/Tools
    • None

    Description

      There;s an asymmetry to how we treat these, with all four legacy commands (read, write, counter_read, counter_write) getting their own full-blown command, whereas the "user" command is comparatively almost hidden. There are also two option sets that apply only to the legacy commands ("schema" and "cols") which isn't at all apparent.

      We should clean this up, by e.g. renaming "user" to "profile" or something more obvious, and dropping the four old commands and renaming "mixed" to "simple" - this would give "simple" a similar spec style to "profile". We should then make it clear that "cols" and "schema" only apply to the "simple" mode, and should fail if they are supplied otherwise.

      We can of course continue to accept all of the old ways of specifying commands if we want, and just not print them out in the help.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              benedict Benedict Elliott Smith
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: