hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1728) Column family scoping and cluster identification
Date Tue, 16 Feb 2010 18:59:28 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834384#action_12834384

Jean-Daniel Cryans commented on HBASE-1728:

Also note the danger in having a code-oriented 'default' scope that is being written into
every single record. Not that the default would ever change, but we should observe the lessons
of https://issues.apache.org/jira/browse/HBASE-2213 in recording defaults in every HCD.

I will be happy to change it when we have a better solution for all configurations.

What about table level attributes? For those tables with a lot of families it might make life

Will it be easier or more complicated? Is setting the scope on 5 families that hard? My feeling
is that we can add it later if we really have people asking for it, in the mean time the code
is less complicated.

> Column family scoping and cluster identification
> ------------------------------------------------
>                 Key: HBASE-1728
>                 URL: https://issues.apache.org/jira/browse/HBASE-1728
>             Project: Hadoop HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.21.0
>         Attachments: HBASE-1728.patch, HCD-family-scoping.patch, HLogKey-scoping.patch
> Support column family scoping via a new HCD attribute. Provide initial set of scoping
constants and javadoc setting expectations for a simple default binary scoping policy: replicate,
or do not. Make the underlying type Integer so more complex edit routing policies are possible.
Also identify every HLogKey with the original cluster's ID.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message