apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From siyuanh <...@git.apache.org>
Subject [GitHub] incubator-apex-malhar pull request: New Kafka input operator using...
Date Tue, 15 Dec 2015 18:37:51 GMT
GitHub user siyuanh opened a pull request:


    New Kafka input operator using 0.9.0 Kafka consumer API

    Some highlights of the operator
     1. Out-of-box One-to-one and one-to-many partition scheme support plus customizable partition
     2. Fault-tolerant when the input operator goes down, it redeploys on other node
     3. At-least-once semantics for operator failure (no matter which operator fails)
     4. At-least-once semantics for cold restart (no data loss even if you restart the application)
     5. Multi-cluster support, one operator can consume data from more than one kafka clusters
     6. Multi-topic support, one operator can subscribe multiple topics
     7. Throughput control support, you can throttle number of tuple for each streaming window
    Things needs to be done,
    More unit test for different partition scheme, application restart
    More integration test
    Metrics for operator
    Bring back idempotency 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/siyuanh/incubator-apex-malhar MLHR-1904

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #134
commit b68a8ce77b4515f51c58150cb167e6c495c6f62c
Author: Siyuan Hua <hsy541@apache.org>
Date:   2015-12-15T18:35:30Z

    Initial commit of new Kafka input operator using 0.9.0 Kafka consumer API


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message