[
https://issues.apache.org/jira/browse/HBASE-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117472#comment-13117472
]
Gary Helmling commented on HBASE-4477:
--------------------------------------
@Todd,
I like the idea of using XXXInfo objects to insulate coprocessors from API
changes they're not using.
@Dhruba,
Agree that it would be better to tackle that in a separate JIRA and keep all of
the APIs in sync. Adopting just PutInfo here would leave us with an oddly
inconsistent API after this patch.
@All,
Can we drop the "CP" prefix and just use PutInfo, GetInfo, DeleteInfo, etc? It
looks ugly to me and unnecessary if we place these classes under
o.a.h.h.coprocessor for namespacing.
Also, I like that this makes the exposed Observer APIs less brittle, but it
does add a fair amount of complexity to the APIs in new classes. To carry this
through, we really need a XXXInfo class per operation...
> 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
