[
https://issues.apache.org/jira/browse/HBASE-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115006#comment-13115006
]
Jonathan Gray commented on HBASE-4477:
--------------------------------------
I think this will take a few changes to the Coprocessor API if we want to only
use RegionObserver and WALObserver.
Andy, what should one do if additional arguments are needed to, say, the
prePut() call? Do we add multiple prePut() calls to the RegionObserver
interface? Potentially deprecate the old ones?
If things are built only on Coprocessor interfaces, do people see us including
these in some kind of coprocessor contrib or should they be out on github or
something?
> 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
