You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Stig Rohde Døssing (JIRA)" <ji...@apache.org> on 2018/11/29 18:20:01 UTC

[jira] [Resolved] (STORM-3290) Split storm-kafka-client KafkaSpoutConfig into a config for the Storm spout and a config for the Trident spouts

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

Stig Rohde Døssing resolved STORM-3290.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

> Split storm-kafka-client KafkaSpoutConfig into a config for the Storm spout and a config for the Trident spouts
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: STORM-3290
>                 URL: https://issues.apache.org/jira/browse/STORM-3290
>             Project: Apache Storm
>          Issue Type: Task
>          Components: storm-kafka-client
>    Affects Versions: 2.0.0
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.0.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The KafkaSpoutConfig class is being used for configuration of both the Trident and non-Trident spouts. I think we should split it up, because about half the properties are only used by the non-Trident spout. It is confusing for users to have a lot of settings that don't do anything.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)