[
https://issues.apache.org/jira/browse/HBASE-11792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140052#comment-15140052
]
Hudson commented on HBASE-11792:
--------------------------------
SUCCESS: Integrated in HBase-Trunk_matrix #693 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/693/])
HBASE-11792 Organize Performance Evaluation usage output (mstanleyjones: rev
7cab24729d4585689af745df179d6ae92b2a6248)
* hbase-server/src/test/java/org/apache/hadoop/hbase/PerformanceEvaluation.java
*
hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/PerformanceEvaluation.java
> 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
> Fix For: 2.0.0
>
> 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)
