[
https://issues.apache.org/jira/browse/HBASE-20505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466564#comment-16466564
]
Andrew Purtell commented on HBASE-20505:
----------------------------------------
Rebased patches.
Tested manually on a cluster.
Used {{./bin/hbase pe --nomapred --rows=1000000 --families=10 randomWrite 1}}
to write 1M rows with 10 families
Verified expected 10 family schema with the shell.
Then, {{./bin/hbase pe --nomapred --rows=100 --families=1 scanRange1000 1}} to
read ranges of 1000 rows over one of the families.
Then, {{./bin/hbase pe --nomapred --rows=100 --families=10 scanRange1000 1}} to
read ranges of 1000 rows over all ten of the families. Bytes per result in scan
metrics is the expected ~10x of the single family run.
Mind if I put this in branch-2.0 along with the rest [~stack] ?
> PE should support multi column family read and write cases
> ----------------------------------------------------------
>
> Key: HBASE-20505
> URL: https://issues.apache.org/jira/browse/HBASE-20505
> Project: HBase
> Issue Type: Test
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.3.3, 2.0.1, 1.4.5
>
> Attachments: HBASE-20505-branch-1.patch, HBASE-20505.patch
>
>
> PerformanceEvaluation has a --columns parameter but this adjusts the number
> of distinct column qualifiers to write (and, with --addColumns, to add to the
> scan), not the number of column families.
> We need something like a new --families parameter that will increase the
> number of column families defined in the test table schema, written to, and
> included in gets and scans. Default is 1, current behavior.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
