[
https://issues.apache.org/jira/browse/HBASE-12884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell resolved HBASE-12884.
-----------------------------------------
Resolution: Won't Fix
> Asynchronous Event Notification in HBase
> -----------------------------------------
>
> Key: HBASE-12884
> URL: https://issues.apache.org/jira/browse/HBASE-12884
> Project: HBase
> Issue Type: New Feature
> Reporter: Shaohui Liu
> Priority: Major
>
> *Background*
> In many scenarios, we need an asynchronous event notification
> mechanism on HBase to know which data have been changed and users can do some
> pre-defined reactions to these events.
> For example:
> * Incremental statistics of data in HBase
> * Audit about change of important data
> * To clean invalid data in other cache systems
> *Features maybe*
> * The mechanism is scalable.
> * The notification is asynchronous. We don't want to affect the write
> performance of HBase.
> * The notification is reliable. The events can't be lost, but we can tolerate
> duplicated events.
> *Solution Maybe*
> * Event notification based on replication. Transform the WAL edits to events,
> and replicates a special peer that users implements.
> This is just a brief thought about this feature. Discussions and suggestions
> are welcomed! Thanks.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
