[ https://issues.apache.org/jira/browse/HBASE-18059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443798#comment-16443798 ]
Hudson commented on HBASE-18059: -------------------------------- Results for branch branch-2 [build #632 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/632/]: (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-2/632//General_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-2/632//JDK8_Nightly_Build_Report_(Hadoop2)/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/632//JDK8_Nightly_Build_Report_(Hadoop3)/] (/) {color:green}+1 source release artifact{color} -- See build output for details. > The scanner order for memstore scanners are wrong > ------------------------------------------------- > > Key: HBASE-18059 > URL: https://issues.apache.org/jira/browse/HBASE-18059 > Project: HBase > Issue Type: Bug > Components: regionserver, scan, Scanners > Affects Versions: 2.0.0 > Reporter: Duo Zhang > Assignee: Jingyun Tian > Priority: Critical > Fix For: 3.0.0, 2.1.0 > > Attachments: HBASE-18059.master.001.patch > > > This is comments for KeyValueScanner.getScannerOrder > {code:title=KeyValueScanner.java} > /** > * Get the order of this KeyValueScanner. This is only relevant for > StoreFileScanners and > * MemStoreScanners (other scanners simply return 0). This is required for > comparing multiple > * files to find out which one has the latest data. StoreFileScanners are > ordered from 0 > * (oldest) to newest in increasing order. MemStoreScanner gets LONG.max > since it always > * contains freshest data. > */ > long getScannerOrder(); > {code} > As now we may have multiple memstore scanners, I think the right way to > select scanner order for memstore scanner is to ordered from Long.MAX_VALUE > in decreasing order. > But in CompactingMemStore and DefaultMemStore, the scanner order for memstore > scanner is also start from 0, which will be messed up with StoreFileScanners. -- This message was sent by Atlassian JIRA (v7.6.3#76005)