You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Hugo Louro (JIRA)" <ji...@apache.org> on 2016/12/09 16:38:58 UTC

[jira] [Commented] (STORM-1765) KafkaBolt with new producer api should be part of storm-kaka-client

    [ https://issues.apache.org/jira/browse/STORM-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735732#comment-15735732 ] 

Hugo Louro commented on STORM-1765:
-----------------------------------

[~revans2] does this JIRA still make sense in face of your recent PR https://github.com/apache/storm/pull/1808

> KafkaBolt with new producer api should be part of storm-kaka-client
> -------------------------------------------------------------------
>
>                 Key: STORM-1765
>                 URL: https://issues.apache.org/jira/browse/STORM-1765
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Sriharsha Chintalapani
>            Assignee: Hugo Louro
>
> During the discussion of storm-kaka-client we agreed on following
> "We talked about this some more and it seems to me it would make more sense to leave this new spout in storm-kafka-client (or whatever you want to call it) and move the KafkaBolt which uses the new producer api over here also. That way this component only needs to depend on the new kafka-clients java api and not on the entire scala kafka core. We can make the old storm-kafka depend on this component so it still picks up the bolt so if anyone is using that its still works. We can deprecate the old KafkaSpout but keep it around for people using older versions of Kafka - tgravescs"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)