GitHub user vahidhashemian opened a pull request:

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

    KAFKA-3982: Fix processing order of some of the consumer properties

    This PR updates processing of console consumer's input properties.
    
    For both old and new consumer, the value provided for `auto.offset.reset` 
indirectly through `consumer.config` or `consumer.property` arguments will now 
take effect.
    For new consumer and for `key.deserializer` and `value.deserializer` 
properties, the precedence order is fixed to first the value directly provided 
as an argument, then the value provided indirectly via `consumer.property` and 
then `consumer.config`, and finally a default value.

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

    $ git pull https://github.com/vahidhashemian/kafka KAFKA-3982

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

    https://github.com/apache/kafka/pull/1655.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 #1655
    
----
commit 6e112c8d097d55cbd5cd6dd81077180b89f175e3
Author: Vahid Hashemian <vahidhashem...@us.ibm.com>
Date:   2016-07-22T20:48:59Z

    KAFKA-3982: Fix processing order of some of the consumer properties
    
    This PR updates processing of console consumer's input properties.
    
    For both old and new consumer, the value provided for `auto.offset.reset` 
indirectly through `consumer.config` or `consumer.property` arguments will now 
take effect.
    For new consumer and for `key.deserializer` and `value.deserializer` 
properties, the precedence is fixed to first the value directly provided as an 
argument, then the value provided indirectly via `consumer.property` and then 
`consumer.config`, and finally a default value.

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to