[
https://issues.apache.org/jira/browse/HBASE-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116675#comment-13116675
]
Andrew Purtell commented on HBASE-4477:
---------------------------------------
@dhruba
bq. can I change the signature of RegionObserver.prePut() to take in two
additional arguments: a WALEdit and Put object
That sounds good. Since there is no release yet, no deprecation is necessary.
Can be done simply by a patch on this issue I'd say.
@Jon
bq. 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
I think it depends. Some stuff like security we'd clearly want to bundle. And
by that not a resurrection of contrib, instead as another package in main/.
Random additions that people build for themselves should go up on GitHub. My
opinion is anything that is core to a group of use cases is a candidate for
bundling, if a contributor or committer wants to maintain it, and/or if people
generally feel it is a good idea to bring the candidate in.
> 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
