[
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)
