hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4477) Ability for an application to store metadata into the transaction log
Date Wed, 28 Sep 2011 03:45:45 GMT

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

dhruba borthakur commented on HBASE-4477:
-----------------------------------------

@Andrew: I would like to do this via a co-processor API, can I change the signature of RegionObserver.prePut()
to take in two additional arguments: a WALEdit and Put object? If so, shall I mark the existing
prePut precessor api as Deprecated?

anybody else have any opinions on where to put the code that implements this functionality?
One place is org.apache.hadoop.hbase.coprocessor.library.walMetadata. 
                
> Ability for an application to store metadata into the transaction log
> ---------------------------------------------------------------------
>
>                 Key: HBASE-4477
>                 URL: https://issues.apache.org/jira/browse/HBASE-4477
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: hlogMetadata1.txt
>
>
> mySQL allows an application to store an arbitrary blob along with each transaction in
its transaction logs. This JIRA is to have a similar feature request for HBASE.
> The use case is as follows: An application on one data center A stores a blob of data
along with each transaction. A replication software picks up these blobs from the transaction
logs in A and hands it to another instance of the same application running on a remote data
center B. The application in B is responsible for applying this to the remote Hbase cluster
(and also handle conflict resolution if any).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message