[
https://issues.apache.org/jira/browse/HBASE-21545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719532#comment-16719532
]
Andrey Elenskiy commented on HBASE-21545:
-----------------------------------------
The assertion in checkVersions() seems to be another bug in
NEW_VERSION_BEHAVIOR. Since NEW_VERSION_BEHAVIOR changes how versioning for
deleted cells is accounted, we should expect to deleted cells to be checked. In
fact it states so in "match()" of MajorCompactionScanQueryMatcher "7. Delete
marker need to be version counted together with puts the affect". Should I open
a new bug for this? Also what do you want to do about failed tests, should a
new set of UTs be written for NEW_VERSION_BEHAVIOR where it differs with
default one?
> NEW_VERSION_BEHAVIOR breaks Get/Scan with specified columns
> -----------------------------------------------------------
>
> Key: HBASE-21545
> URL: https://issues.apache.org/jira/browse/HBASE-21545
> Project: HBase
> Issue Type: Bug
> Components: API
> Affects Versions: 2.0.0, 2.1.1
> Environment: HBase 2.1.1
> Hadoop 2.8.4
> Java 8
> Reporter: Andrey Elenskiy
> Assignee: Andrey Elenskiy
> Priority: Major
> Attachments: App.java, HBASE-21545.branch-2.1.0001.patch,
> HBASE-21545.branch-2.1.0002.patch, HBASE-21545.branch-2.1.0003.patch,
> HBASE-21545.branch-2.1.0004.patch, HBASE-21545.branch-2.1.0005.patch
>
>
> Setting NEW_VERSION_BEHAVIOR => 'true' on a column family causes only one
> column to be returned when columns are specified in Scan or Get query. The
> result is always one first column by sorted order. I've attached a code
> snipped to reproduce the issue that can be converted into a test.
> I've also validated with hbase shell and gohbase client, so it's gotta be
> server side issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
