Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@kafka.apache.org
Date: Mon, 11 Dec 2017 19:05:00 +0000 (UTC)
From: "Guozhang Wang (JIRA)" <jira@apache.org>
To: jira@kafka.apache.org
Message-ID: <JIRA.12747889.1413244973000.432584.1513019100837@Atlassian.JIRA>
In-Reply-To: <JIRA.12747889.1413244973000@Atlassian.JIRA>
References: <JIRA.12747889.1413244973000@Atlassian.JIRA> <JIRA.12747889.1413244973328@jira-lw-us.apache.org>
Subject: [jira] [Updated] (KAFKA-1704) Add PartitionConfig besides LogConfig
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 11 Dec 2017 19:05:07 -0000


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

Guozhang Wang updated KAFKA-1704:
---------------------------------
    Description: 
Today we only have two places to store configs: server configs which is used to store server side global configs, and log configs to store others. However, many topic / partition level configs would be better stored in a partition config such that they do not need to require accessing the underlying logs, for example:

1. uncleanLeaderElectionEnable
2. minInSyncReplicas
3. compact [? this is defined per-topic / partition but maybe ok to store as log configs]

  was:
Today we only two places to store configs: server configs which is used to store server side global configs, and log configs to store others. However, many topic / partition level configs would be better stored in a partition config such that they do not need to require accessing the underlying logs, for example:

1. uncleanLeaderElectionEnable
2. minInSyncReplicas
3. compact [? this is defined per-topic / partition but maybe ok to store as log configs]


> Add PartitionConfig besides LogConfig
> -------------------------------------
>
>                 Key: KAFKA-1704
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1704
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Guozhang Wang
>            Assignee: Guozhang Wang
>              Labels: newbie
>
> Today we only have two places to store configs: server configs which is used to store server side global configs, and log configs to store others. However, many topic / partition level configs would be better stored in a partition config such that they do not need to require accessing the underlying logs, for example:
> 1. uncleanLeaderElectionEnable
> 2. minInSyncReplicas
> 3. compact [? this is defined per-topic / partition but maybe ok to store as log configs]


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