Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D715A200C64 for ; Fri, 28 Apr 2017 21:39:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D5981160BA3; Fri, 28 Apr 2017 19:39:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 271A1160B95 for ; Fri, 28 Apr 2017 21:39:14 +0200 (CEST) Received: (qmail 52785 invoked by uid 500); 28 Apr 2017 19:39:08 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 52644 invoked by uid 99); 28 Apr 2017 19:39:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Apr 2017 19:39:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 9BCC2CA98A for ; Fri, 28 Apr 2017 19:39:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id CUq_AXxEuwzJ for ; Fri, 28 Apr 2017 19:39:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id E7C055FAE8 for ; Fri, 28 Apr 2017 19:39:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D3E91E0D45 for ; Fri, 28 Apr 2017 19:39:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3558B21DE5 for ; Fri, 28 Apr 2017 19:39:04 +0000 (UTC) Date: Fri, 28 Apr 2017 19:39:04 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-5096) Only log invalid user configs and overwrite with correct one MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 28 Apr 2017 19:39:15 -0000 [ https://issues.apache.org/jira/browse/KAFKA-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989348#comment-15989348 ] ASF GitHub Bot commented on KAFKA-5096: --------------------------------------- GitHub user johnma14 opened a pull request: https://github.com/apache/kafka/pull/2938 KAFKA-5096: Log invalid user configs and use defaults Kafka Streams do not allow users to modify some consumer configurations. If the user modifies this property, currently an exception is thrown. The following changes were made in this patch: - Defined a new array 'NON_CONFIGURABLE_CONSUMER_CONFIGS' to hold the names of the configuration parameters that is not allowed to be modified. Currently, this contains just 1 parameter - enable_auto_commit. When the 'exactly once' feature is implemented ( KAFKA-4923), more parameters can be added to this array. - Defined a new method 'checkIfUnexpectedUserSpecifiedConsumerConfig' to check if user overwrote the values of any of the non configurable configuration parameters. If so, then log a warning message and reset the default values - Updated the javadoc to include the configuration parameters that cannot be modified by users. - Updated the corresponding tests in StreamsConfigTest.java to reflect the changes made in StreamsConfig.java You can merge this pull request into a Git repository by running: $ git pull https://github.com/johnma14/kafka bug/kafka-5096 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2938.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 #2938 ---- commit 1194fab4c3529cb3745548711a39cf9ec8753f04 Author: Mariam John Date: 2017-04-28T18:32:54Z KAFKA-5096: Log invalid user configs and use defaults Kafka Streams do not allow users to modify some consumer configurations. Currently, it does not allow modifying the value of 'enable_auto_commit'. If the user modifies this property, currently an exception is thrown. The following changes were made in this patch: - Defined a new array 'NON_CONFIGURABLE_CONSUMER_CONFIGS' to hold the names of the configuration parameters that is not allowed to be modified - Defined a new method 'checkIfUnexpectedUserSpecifiedConsumerConfig' to check if user overwrote the values of any of the non configurable configuration parameters. If so, then log a warning message and reset the default values - Updated the javadoc to include the configuration parameters that cannot be modified by users. - Updated the corresponding tests in StreamsConfigTest.java to reflect the changes made in StreamsConfig.java ---- > Only log invalid user configs and overwrite with correct one > ------------------------------------------------------------ > > Key: KAFKA-5096 > URL: https://issues.apache.org/jira/browse/KAFKA-5096 > Project: Kafka > Issue Type: Improvement > Components: streams > Reporter: Matthias J. Sax > Assignee: Mariam John > Priority: Minor > Labels: beginner, newbie > > Streams does not allow to overwrite some config parameters (eg, {{enable.auto.commit}}) Currently, we throw an exception, but this is actually not required, as Streams can just ignore/overwrite the user provided value. > Thus, instead of throwing, we should just log a WARN message and overwrite the config with the values that suits Streams. (atm it's only one parameter {{enable.auto.commit}}), but with exactly-once it's going to be more (cf. KAFKA-4923). Thus, the scope of this ticket depends when it will be implemented (ie, before or after KAFKA-4923). > This ticket should also include JavaDoc updates that explain what parameters cannot be specified by the user. -- This message was sent by Atlassian JIRA (v6.3.15#6346)