[ 
https://issues.apache.org/jira/browse/KAFKA-16863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850587#comment-17850587
 ] 

A. Sophie Blee-Goldman commented on KAFKA-16863:
------------------------------------------------

If we're going to do a config name cleanup, maybe we can do a pass and fix all 
the current issues. For example I just happened to notice that two of the new 
rack-aware assignment configs use underscores in part of their config name, 
which does not follow the establish pattern and is likely to be messed up 
easily by users who depend on config files or otherwise configure things 
without the aid of the java config variable

For example "rack.aware.assignment.traffic_cost" should be 
"rack.aware.assignment.traffic.cost"

These are very new configs so maybe the disruption isn't worth it. On the other 
hand, if we can make this change now, maybe we can fix it before too many 
people start using the new feature and these underscore-based configs?

> Consider removing `default.` prefix for exception handler config
> ----------------------------------------------------------------
>
>                 Key: KAFKA-16863
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16863
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Matthias J. Sax
>            Priority: Trivial
>              Labels: need-kip
>
> Kafka Streams has a set of configs with `default.` prefix. The intent for the 
> default-prefix is to make a distinction between, well the default, and 
> in-place overwrites in the code. Eg, users can specify ts-extractors on a 
> per-topic basis.
> However, for the deserialization- and production-exception handlers, no such 
> overwrites are possible, and thus, `default.` does not really make sense, 
> because there is just one handler overall. Via KIP-1033 we added a new 
> processing-exception handler w/o a default-prefix, too.
> Thus, we should consider to deprecate the two existing configs names and add 
> them back w/o the `default.` prefix.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to