You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/08/01 03:08:04 UTC

[jira] [Updated] (HBASE-14154) DFS Replication should be configurable at column family level

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

Andrew Purtell updated HBASE-14154:
-----------------------------------
    Attachment: HBASE-14154-v4.patch

TestFromClientSide is indeed failing.
{noformat}
testIllegalTableDescriptor(org.apache.hadoop.hbase.client.TestFromClientSide)  Time elapsed: 29.729 sec  <<< FAILURE!
java.lang.AssertionError: Should throw exception if value is explicitly being set to 0
	at org.junit.Assert.fail(Assert.java:88)
	at org.apache.hadoop.hbase.client.TestFromClientSide.testIllegalTableDescriptor(TestFromClientSide.java:5535)
{noformat}

The test case was changed in the v3 patch. (FYI, 0 is not an illegal value for the API, it means "use default FS settings") v4 addresses the issue. I'm going to commit shortly unless objection.

> DFS Replication should be configurable at column family level
> -------------------------------------------------------------
>
>                 Key: HBASE-14154
>                 URL: https://issues.apache.org/jira/browse/HBASE-14154
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Ashish Singhi
>            Assignee: Ashish Singhi
>            Priority: Minor
>             Fix For: 2.0.0, 0.98.14, 1.3.0
>
>         Attachments: HBASE-14154-0.98-v1.patch, HBASE-14154-0.98.patch, HBASE-14154-branch-1-v1.patch, HBASE-14154-branch-1.patch, HBASE-14154-v1.patch, HBASE-14154-v2.patch, HBASE-14154-v3.patch, HBASE-14154-v4.patch, HBASE-14154.patch
>
>
> There are cases where a user wants to have a control on the number of hfile copies he/she can have in the cluster.
> For eg: For a test table user would like to have only one copy instead of three(default).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)