[ https://issues.apache.org/jira/browse/HBASE-11792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Misty Stanley-Jones updated HBASE-11792: ---------------------------------------- Attachment: HBASE-11792-branch-1.patch HBASE-11792-branch-1.0.patch HBASE-11792-branch-1.1.patch HBASE-11792-branch-1.2.patch HBASE-11792-0.98.patch I wasn't sure what branches should get this change so I made these. > Organize PerformanceEvaluation usage output > ------------------------------------------- > > Key: HBASE-11792 > URL: https://issues.apache.org/jira/browse/HBASE-11792 > Project: HBase > Issue Type: Improvement > Components: Performance, test > Reporter: Nick Dimiduk > Assignee: Misty Stanley-Jones > Priority: Minor > Labels: beginner > Attachments: HBASE-11792-0.98.patch, HBASE-11792-branch-1.0.patch, > HBASE-11792-branch-1.1.patch, HBASE-11792-branch-1.2.patch, > HBASE-11792-branch-1.patch, HBASE-11792.patch > > > PerformanceEvaluation has enjoyed a good bit of attention recently. All the > new features are muddled together. It would be nice to organize the output of > the Options list according to some scheme. I was thinking you're group > entries by when they're used. For example > *General options* > - nomapred > - rows > - oneCon > - ... > *Table Creation/Write tests* > - compress > - flushCommits > - valueZipf > - ... > *Read tests* > - filterAll > - multiGet > - replicas > - ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)