[ 
https://issues.apache.org/jira/browse/HBASE-21545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-21545:
--------------------------
    Attachment: Screen Shot 2018-12-24 at 10.04.57 AM.png

> 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
>              Labels: NEW_VERSION_BEHAVIOR
>             Fix For: 3.0.0, 2.2.0, 2.1.2, 2.0.4
>
>         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, Screen 
> Shot 2018-12-24 at 10.04.57 AM.png
>
>
> 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)

Reply via email to