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 21:23:27 GMT

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

Jean-Daniel Cryans commented on HBASE-1728:

bq. Does this mean that only one cluster can be associated with one zk instance? Or is the
notion that if mutliple clusters are sharing the one zk ensemble, then they will be homed
(gaol'd) at different areas up in zk ( I suppose that makes sense - huh - they'd have to be)

I like the way you are able to answer yourself. Yes they have different home dir so it's ok

bq. The change to HLogKey means we can't read old logs. Thats probably fine, right? Migration
requires that there be no hlogs in filesystem?

Right, major version change. Although I did this:
    try {
      this.clusterId = in.readByte();
      this.scope = in.readInt();
    } catch(EOFException e) {
      // Means it's an old key, just continue

Will commit with your comments-related fixes. Thanks!

> 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