Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-3982

Issue with processing order of consumer properties in console consumer

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 0.11.0.0
    • consumer
    • None

    Description

      With the recent introduction of consumer.property argument in console consumer, both new and old consumer could overwrite certain properties provided using this new argument.

      Specifically, the old consumer would overwrite the values provided for auto.offset.reset and zookeeper.connect, and the new consumer would overwrite the values provided for auto.offset.reset, bootstrap.servers, key.deserializer, and key.deserializer.

      For example, running the old consumer as bin/kafka-console-consumer.sh --zookeeper localhost:2181 --topic foo --consumer-property auto.offset.reset=none the value that's eventually selected for auto.offset.reset will be largest, overwriting what the user provides in the command line.

      This seems to be because the properties provided via consumer.property argument are not considered when finalizing the configuration of the consumer.

      Some properties can now be provided in three different places (directly in the command line, via the consumer.property argument, and via the consumer.config argument, in the same order of precedence).

      Attachments

        Issue Links

          Activity

            People

              vahid Vahid Hashemian
              vahid Vahid Hashemian
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: