[
https://issues.apache.org/jira/browse/HBASE-21545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709353#comment-16709353
]
Andrey Elenskiy commented on HBASE-21545:
-----------------------------------------
Oh, I'm not planning on working on a fix as I don't have enough knowledge about
the moving pieces. [~busbey] asked for a reproduction test so I converted it :)
On a side note, this seems like a bug that should have been caught by existing
tests if they were converted to use new version behavior attribute. Do you
think ti would be possible to run all the tests again with this option enabled
by default and see what other bugs come out?
> 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.1.1
> Environment: HBase 2.1.1
> Hadoop 2.8.4
> Java 8
> Reporter: Andrey Elenskiy
> Assignee: Sakthi
> Priority: Major
> Attachments: App.java, HBASE-21545.branch-2.1.0001.patch,
> HBASE-21545.branch-2.1.0002.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)
