hbase-issues mailing list archives

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

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

Todd Lipcon commented on HBASE-4477:
------------------------------------

Just a thought while we're changing the APIs: might make sense to do something like introduce
the following interface:
{code}
interface CPPutInfo {
  public Put getPutObject();
  public boolean getWriteToWAL();
  public WALEdit getWalEdit();
}
{code}

then, if we want to extend this API with more info about the put later, we can simply add
more methods and not break compatibility? We should probably do this in another JIRA, and
for all of the RegionObserver hooks - this JIRA just gave me the idea.
                
> 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: coprocessorPut1.txt, 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