[
https://issues.apache.org/jira/browse/HBASE-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-4477:
----------------------------------
Attachment: coprocessorPut2.txt
+1
Attached updated patch 'coprocessorPut2.txt" which removes some unused locals.
I'm curious if passing the cluster ID to internalPut and internalDelete is
necessary? They can be retrieved from the Put or Delete, or the Put or Delete
can be modified. I don't know enough about replication there: The put or delete
gets written to the WAL with one UUID but internally contains another?
> 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, coprocessorPut2.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
