[
https://issues.apache.org/jira/browse/HBASE-19749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16321751#comment-16321751
]
Hudson commented on HBASE-19749:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4380 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/4380/])
HBASE-19749 Revisit logic of UserScanQueryMatcher#mergeFilterResponse (openinx:
rev 8bf6adbe75aa5a43b3fa960c54a4aa544b51f128)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/querymatcher/TestUserScanQueryMatcher.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/querymatcher/UserScanQueryMatcher.java
> Revisit logic of UserScanQueryMatcher#mergeFilterResponse method
> -----------------------------------------------------------------
>
> Key: HBASE-19749
> URL: https://issues.apache.org/jira/browse/HBASE-19749
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-1
> Reporter: Zheng Hu
> Assignee: Zheng Hu
> Fix For: 2.0.0-beta-1
>
> 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)
