You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2018/05/02 01:17:00 UTC
[jira] [Updated] (HBASE-20517) Fix PerformanceEvaluation 'column'
parameter
[ https://issues.apache.org/jira/browse/HBASE-20517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-20517:
-----------------------------------
Attachment: HBASE-20517-branch-1-WIP.patch
> Fix PerformanceEvaluation 'column' parameter
> --------------------------------------------
>
> Key: HBASE-20517
> URL: https://issues.apache.org/jira/browse/HBASE-20517
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 2.0.1, 1.4.5
>
> Attachments: HBASE-20517-branch-1-WIP.patch
>
>
> PerformanceEvaluation's 'column' parameter looks broken to me.
> To test:
> 1. Write some data with 20 columns.
> 2. Do a scan test selecting one column.
> 3. Do a scan test selecting ten columns.
> You'd expect the amount of data returned to vary but no, because the read side isn't selecting the same qualifiers that are written. Bytes returned in case 3 should be 10x those in case 2.
> I'm in branch-1 code at the moment. Probably affects trunk too.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)