hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2361) WALEdit broke replication scope
Date Tue, 30 Mar 2010 03:35:27 GMT

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

stack commented on HBASE-2361:

+1 on commit

> WALEdit broke replication scope
> -------------------------------
>                 Key: HBASE-2361
>                 URL: https://issues.apache.org/jira/browse/HBASE-2361
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.21.0
>         Attachments: HBASE-2361-2.patch, HBASE-2361-3.patch, HBASE-2361.patch
> Before HBASE-2283, each KV had a HLogKey with a replication scope. Now a key applies
to a list of KVs that spans multiple families so a single scope doesn't work anymore. Multiple
possible solutions:
>  - Each KV have their own scope. We already ruled that out in a previous jira since that
means the scope would end up in the HFiles.
>  - Store pairs of scope/KV in WALEdit instead of straight KVs.
>  - Have 2 parallel lists in WALEdit, one for KVs and the other for scopes.
>  - Subclass KV and add the scope there, those would be created when inserted in the WAL
and would contain the KV stored in the HFiles.
> I'm sure there are other solutions, discuss.

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

View raw message