[
https://issues.apache.org/jira/browse/KAFKA-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-2914.
------------------------------------------
Resolution: Won't Fix
[~apurtell] Thanks for the link. I'm going to mark this "Won't Fix" since the
Kafka project is taking a federated approach to connector development and won't
be including connectors within the project itself. Hopefully HBase connector
development can be picked up at the link you've provided.
> Kafka Connect Source connector for HBase
> -----------------------------------------
>
> Key: KAFKA-2914
> URL: https://issues.apache.org/jira/browse/KAFKA-2914
> Project: Kafka
> Issue Type: New Feature
> Components: copycat
> Reporter: Niels Basjes
> Assignee: Ewen Cheslack-Postava
>
> In many cases I see HBase being used to persist data.
> I would like to listen to the changes and process them in a streaming system
> (like Apache Flink).
> Feature request: A Kafka Connect "Source" that listens to the changes in a
> specified HBase table. These changes are then stored in a 'standardized' form
> in Kafka so that it becomes possible to process the observed changes in
> near-realtime. I expect this 'standard' to be very HBase specific.
> Implementation suggestion: Perhaps listening to the HBase WAL like the "HBase
> Side Effects Processor" does?
> https://github.com/NGDATA/hbase-indexer/tree/master/hbase-sep
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
