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

ASF GitHub Bot commented on KAFKA-4361:
---------------------------------------

GitHub user dguy opened a pull request:

    https://github.com/apache/kafka/pull/2084

    KAFKA-4361: Streams does not respect user configs for "default" params

    Enable user provided consumer and producer configs to override the streams 
default configs. 

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

    $ git pull https://github.com/dguy/kafka kafka-4361

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

    https://github.com/apache/kafka/pull/2084.patch

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

    This closes #2084
    
----
commit 47f428940fa05d3c733832cf0e228d3a93a102e3
Author: Damian Guy <damian....@gmail.com>
Date:   2016-11-01T10:18:55Z

    override StreamsConfig consumer and producer defaults

----


> Streams does not respect user configs for "default" params
> ----------------------------------------------------------
>
>                 Key: KAFKA-4361
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4361
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.10.1.0
>            Reporter: Roger Hoover
>            Assignee: Damian Guy
>
> For the config params in CONSUMER_DEFAULT_OVERRIDES 
> (https://github.com/apache/kafka/blob/0.10.1/streams/src/main/java/org/apache/kafka/streams/StreamsConfig.java#L274)
>  such as consumer.max.poll.records and consumer.auto.offset.reset, those 
> parameters are not used and instead overridden by the defaults.  It may not 
> work for some producer config values as well.
> If your application sets those params in the StreamsConfig, they are not used 
> in the underlying Kafka Consumers (and possibly Producers)



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

Reply via email to