[ https://issues.apache.org/jira/browse/HBASE-19749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zheng Hu updated HBASE-19749: ----------------------------- Attachment: HBASE-19749.v1.patch > Revisit logic of UserScanQueryMatcher#mergeFilterResponse method > ----------------------------------------------------------------- > > Key: HBASE-19749 > URL: https://issues.apache.org/jira/browse/HBASE-19749 > Project: HBase > Issue Type: Bug > Reporter: Zheng Hu > Assignee: Zheng Hu > Attachments: HBASE-19749.v1.patch, HBASE-19749.v1.patch > > > As HBASE-19729 comment , there are following points to be optimized: > 1. when the number of cells exceed max version in scan, we should return > SEEK_NEXT_COL match code, but if current code is INCLUDE_AND_SEEK_NEXT_ROW, > we can optimize to choose the max step between SEEK_NEXT_COL and > INCLUDE_AND_SEEK_NEXT_ROW, which is SEEK_NEXT_ROW > 2. check to call ColumnTracker#doneWithColumn() only when we change the > match code to SEEK_NEXT_COL or INCLUDE_AND_SEEK_NEXT_COL because of > filterResponse. > 3. More UT for those edge case.. > https://issues.apache.org/jira/browse/HBASE-19729?focusedCommentId=16318131&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16318131 -- This message was sent by Atlassian JIRA (v6.4.14#64029)