[ https://issues.apache.org/jira/browse/HBASE-21520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722293#comment-16722293 ]
Hudson commented on HBASE-21520: -------------------------------- Results for branch branch-1.2 [build #589 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/589/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (/) {color:green}+1 general checks{color} -- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/589//General_Nightly_Build_Report/] (x) {color:red}-1 jdk7 checks{color} -- For more information [see jdk7 report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/589//JDK7_Nightly_Build_Report/] (x) {color:red}-1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/589//JDK8_Nightly_Build_Report_(Hadoop2)/] (/) {color:green}+1 source release artifact{color} -- See build output for details. > TestMultiColumnScanner cost long time when using ROWCOL bloom type > ------------------------------------------------------------------ > > Key: HBASE-21520 > URL: https://issues.apache.org/jira/browse/HBASE-21520 > Project: HBase > Issue Type: Improvement > Components: test > Reporter: Zheng Hu > Assignee: Zheng Hu > Priority: Major > Fix For: 3.0.0, 1.5.0, 2.2.0, 1.2.10, 1.4.10, 2.1.3, 2.0.5 > > Attachments: HBASE-21520.branch-1.v4.patch, HBASE-21520.v1.patch, > HBASE-21520.v2.patch, HBASE-21520.v3.patch, HBASE-21520.v4.patch, > TestMultiColumnScanner.png, rowcol.txt > > > The TestMultiColumnScanner is easy to be timeout, you can see HBASE-21517. > In my localhost, when I set the parameters to be { > Compression.Algorithm.NONE, BloomType.ROW, false }, it took about 5 seconds. > but if I set the parameters to be { Compression.Algorithm.NONE, > BloomType.ROWCOL, false }, it would take about 45 seconds, which means > ROWCOL cost much more time than ROW. > Need to find out what's wrong with this ut. -- This message was sent by Atlassian JIRA (v7.6.3#76005)