Hi Luke,

> "The overly large scope of these variables can cause development issues.”
I want to express that if the variable is public, we can easily find and use it 
by simply accessing `StreamConfig.` during development, 
which increases the risk of misuse. By changing it to private, this problem can 
be avoided.

Thank you!
Best regards,
Jiunn Yang

> Luke Chen <show...@gmail.com> 於 2024年8月29日 上午11:25 寫道:
> 
> Hi Jiunn,
> 
> Thanks for the KIP.
> 
> In the motivation section:
> "The overly large scope of these variables can cause development issues."
> 
> I can't see why a "doc description variable" will cause any development
> issue.
> Could you explain more clearly what problem we have now?
> 
> Thanks.
> Luke
> 
> On Thu, Aug 29, 2024 at 9:43 AM 黃竣陽 <s7133...@gmail.com> wrote:
> 
>> Hello everyone,
>> 
>> I would like to start a discussion about KIP-1085
>> <
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1085%3A+Fix+leaking+*_DOC+variables+in+StreamsConfig
>>> 
>> In this KIP, we plan to deprecate the public doc variables which only used
>> in `StreamConfig`
>> and make them private in a future release.
>> 
>> Any feedback and suggestions for the KIP are welcome in this email thread.
>> 
>> Thank you!
>> Best regards,
>> Jiunn Yang

Reply via email to