[mateczagany]

What does this change?

With key.fields set and 'value.fields-include' = 'ALL', kafka-safe returned NULL for value-format metadata columns, such as debezium-json's value.source.timestamp. The metadata range started at keyProjection.length + valueProjection.length, which counts the key fields twice. It now starts
at the physical field count. Upstream has the same bug (FLINK-41255), and a TODO marks switching to its helper once that's released.

Area

• Runner CLI and Docker image (flink-sql-runner)
• Connectors (connectors)
• Formats (formats)
• Function libraries (stdlib)
• Environment utilities (env-utils)
• Tests and samples (testing)
• Build / CI / dependencies
• Docs (README.md, stdlib-docs)

How did you test it?

Added a case to SafeKafkaDynamicSourceTest that fails without the fix (+I(42,Ada,null) instead of +I(42,Ada,m)). mvn test -pl connectors/kafka-safe-connector passes.

Checklist

• The PR title starts with a type such as feat:, fix: or docs:, optionally with a scope (e.g. fix(flexible-json):)
• mvn clean install passes locally and the code is formatted with mvn spotless:apply
• New or changed behavior is covered by tests (given_when_then naming, AssertJ assertions)
• New dependency and plugin versions are defined as properties in the root pom.xml
• Commits are signed off and signed (git commit -s -S)
• README.md and stdlib-docs are updated if user-facing behavior or functions changed

🤖 Generated with Claude Code