Github user bowenli86 commented on the issue: https://github.com/apache/flink/pull/4473 I'm in favor of the 3rd option. In that way, we don't need to 1) duplicate all KPL keys and documentation to flink-kinesis-connector and 2) always keep an eye on KPL configs when upgrading its version. Since you point out that migrate existing keys is not hard and harmful, I'm leaning even more towards it :) Do we all agree on the approach? @tzulitai @aljoscha
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---