[FLINK-28475] [Connector/kafka] stopping offset can be 0.

[leozhangsr]

What is the purpose of the change

Stopping offset can be 0.When we make a zero stopping offset empty,it would be serialized to NO_STOPPING_OFFSET, which it is not expected. It' had been fixed in master by https://github.com/apache/flink/pull/20234, now need to merge into release-1.14.

Brief change log

change a stopping offset conditon from '>0' to '>=0'

Verifying this change

Can be verified by: KafkaPartitionSplitReaderTest#testAssignEmptySplit KafkaPartitionSplitSerializerTest

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[flinkbot]

CI report:

• efff0ecc753f35ad3980444f319a2109c323c93f Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[leozhangsr]

It has a Compilation failure here,I will modified it later

[leozhangsr]

@flinkbot run azure

[leozhangsr]

@flinkbot run azure

[leozhangsr]

This mr still not merge yet, can anyone help?

[leozhangsr]

Already close since flink0.15