You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2009/09/13 20:25:57 UTC
[jira] Created: (HBASE-1834) Add scoping information to KVs
Add scoping information to KVs
------------------------------
Key: HBASE-1834
URL: https://issues.apache.org/jira/browse/HBASE-1834
Project: Hadoop HBase
Issue Type: Sub-task
Reporter: Andrew Purtell
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1834) Add scoping information to KVs
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754835#action_12754835 ]
Andrew Purtell commented on HBASE-1834:
---------------------------------------
bq. i think the data should go into only HLog and not actually enter KeyValue or the HFile stores
That was my strategy -- put it in HLogKey only and do it one key at a time.
I'll go back and try it again.
> Add scoping information to KVs
> ------------------------------
>
> Key: HBASE-1834
> URL: https://issues.apache.org/jira/browse/HBASE-1834
> Project: Hadoop HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1834) Add scoping information to KVs
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754817#action_12754817 ]
Andrew Purtell commented on HBASE-1834:
---------------------------------------
The main problem I had with not doing it this way is getting to column family metadata from various places in the code, for example HLog.completeCacheFlush(). This was because I was trying to tag HLogKeys with scope as they are written, and thus far scope information is kept in HCD. However it doesn't have to be done that way. A replicator could look up what to do for each KV according to information in the key. No HLogKey or KV would be tagged with any scoping information. However byte[] compares for every KV would be more overhead than modifying the write path to carry scope information along.
Other options?
> Add scoping information to KVs
> ------------------------------
>
> Key: HBASE-1834
> URL: https://issues.apache.org/jira/browse/HBASE-1834
> Project: Hadoop HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1834) Add scoping information to KVs
Posted by "ryan rawson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754814#action_12754814 ]
ryan rawson commented on HBASE-1834:
------------------------------------
this is pretty intrusive (invalidates all older data stores) and I'm not sure its completely necessary to achieve replication.
there is also the question of, how do we do multi-master replication.
> Add scoping information to KVs
> ------------------------------
>
> Key: HBASE-1834
> URL: https://issues.apache.org/jira/browse/HBASE-1834
> Project: Hadoop HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1834) Add scoping information to KVs
Posted by "ryan rawson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754819#action_12754819 ]
ryan rawson commented on HBASE-1834:
------------------------------------
i think the data should go into only HLog and not actually enter KeyValue or the HFile stores. Then we can either ship entire log block segments or do 1 key at a time (preferred).
> Add scoping information to KVs
> ------------------------------
>
> Key: HBASE-1834
> URL: https://issues.apache.org/jira/browse/HBASE-1834
> Project: Hadoop HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-1834) Add scoping information to KVs
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans resolved HBASE-1834.
---------------------------------------
Resolution: Won't Fix
Scoping the KVs is very intrusive, instead that will be done in HLogKey in HBASE-1728.
> Add scoping information to KVs
> ------------------------------
>
> Key: HBASE-1834
> URL: https://issues.apache.org/jira/browse/HBASE-1834
> Project: Hadoop HBase
> Issue Type: Sub-task
> Reporter: Andrew Purtell
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.