Hi, Thanks for the KIP. Personally, I think we are being a bit too timid here. The problem is that the `--delete-config` option is already broken and it cannot be the case that anyone is using it successfully. By removing it in 5.0, we are essentially going to have an option whose help message says “This deprecated option is not supported.”. Really, it should work during its deprecation period. The confusion would arise because it was broken previously.
So, I am in favour of the KIP, but I suggest that it should actually be removed in 4.0 rather than deprecated in 4.0 and then removed in 5.0 because it already doesn’t work. Thanks, Andrew > On 5 Aug 2024, at 06:00, TengYao Chi <kiting...@gmail.com> wrote: > > Hi Chia-Ping > I think your suggestions is fair enough, I will modified the content > proposal and index later. > > Best Regards, > TengYao. > > Chia-Ping Tsai <chia7...@gmail.com> 於 2024年8月5日 週一 下午12:44寫道： > >> hi TengYao >> >> q0: >> users will encounter config error if we remove the config `delete-config`, >> and that is why we need a KIP even `delete-config` is a no-op >> configuration. >> If above description is correct, could you please make motivation include >> it? >> >> q1: >> deleting the config is not critical, and hence we should follow the >> one-year rule. That means the version to delete the config is 5.0 rather >> than 4.0 >> >> Best, >> Chia-Ping >> >> >> TengYao Chi <kiting...@gmail.com> 於 2024年8月5日 週一 下午12:32寫道： >> >>> Hello everyone, >>> I would like to start a discussion about KIP-1079 >>> < >>> >> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1079%3A+Deprecate+%60delete-config%60+of+TopicCommand >>>> . >>> We plan to deprecate the `*delete-config*` command in *TopicCommand*, as >> it >>> is a no-op. >>> Please take a look, and if you have any suggestions or thoughts, feel >> free >>> to reply to this email thread. >>> >>> Thank you! >>> >>> Best regards, >>> TengYao >>> >>
