hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HBASE-15320) HBase connector for Kafka Connect
Date Mon, 24 Apr 2017 06:14:04 GMT

     [ https://issues.apache.org/jira/browse/HBASE-15320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Anoop Sam John reassigned HBASE-15320:

    Assignee: Mike Wingert

> HBase connector for Kafka Connect
> ---------------------------------
>                 Key: HBASE-15320
>                 URL: https://issues.apache.org/jira/browse/HBASE-15320
>             Project: HBase
>          Issue Type: New Feature
>          Components: Replication
>            Reporter: Andrew Purtell
>            Assignee: Mike Wingert
>              Labels: beginner
>             Fix For: 2.0.0
> Implement an HBase connector with source and sink tasks for the Connect framework (http://docs.confluent.io/2.0.0/connect/index.html)
available in Kafka 0.9 and later.
> See also: http://www.confluent.io/blog/announcing-kafka-connect-building-large-scale-low-latency-data-pipelines
> An HBase source (http://docs.confluent.io/2.0.0/connect/devguide.html#task-example-source-task)
could be implemented as a replication endpoint or WALObserver, publishing cluster wide change
streams from the WAL to one or more topics, with configurable mapping and partitioning of
table changes to topics.  
> An HBase sink task (http://docs.confluent.io/2.0.0/connect/devguide.html#sink-tasks)
would persist, with optional transformation (JSON? Avro?, map fields to native schema?), Kafka
SinkRecords into HBase tables.

This message was sent by Atlassian JIRA

View raw message