[ https://issues.apache.org/jira/browse/HBASE-21545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710686#comment-16710686 ]
Andrey Elenskiy commented on HBASE-21545: ----------------------------------------- I've uploaded a patch where I modified HBaseTestingUtility to set NEW_VERSION_BEHAVIOR attribute in integration tests when "-Dhbase.tests.new.version.behavior=true" option is passed. This way we validate that all tests pass with this attribute. Would be great if you could trigger a build. > 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 > > > 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)