[jira] [Updated] (STORM-2826) KafkaSpoutConfig.builder doesn't set key/value deserializer properties in storm-kafka-client

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot updated STORM-2826:
----------------------------------
    Labels: pull-request-available  (was: )

> KafkaSpoutConfig.builder doesn't set key/value deserializer properties in storm-kafka-client
> --------------------------------------------------------------------------------------------
>
>                 Key: STORM-2826
>                 URL: https://issues.apache.org/jira/browse/STORM-2826
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka-client
>    Affects Versions: 1.2.0
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Blocker
>              Labels: pull-request-available
>
> STORM-2548 replaced the KafkaSpoutConfig.builder() implementations with ones that don't set the key/value deserializer fields in KafkaSpoutConfig, but instead just sets the corresponding property in the kafkaProps map. This is a breaking change for applications that assume those properties are set after the builder is created.
> Code like the following would break.
> {quote}
> this.keyDeserializer = config.getKeyDeserializer().getClass();
> this.valueDeserializer = config.getValueDeserializer().getClass();
> {quote}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)