TiKV compatibility tracking issue

[iosmanthus]

Feature Request

Currently, client-java's features are always catching to the latest version of TiKV, it is hard to select the version of TiKV with a specific version of client-java. We are only tracking the compatibility of master and release-3.1's integration tests without each specific API.

Release-3.1 is fully compatible with TiKV (5.0.x - 5.3.x).
The master branch has been discovered the issue: #462.

Describe the feature you'd like:
To draw the full compatibility matrix, we need:

• introducing version constraint on some tests, fix master branch compatibility tracking issue #462 by [to #462] add version constraint for rawkv tests #463.
• use integration tests to cover every exported API, e.g. RawKVClient, PDClient: [to #464] add unit tests for exported API of RawKVClient #471
  • RawKVClient
    • ingest
    • batchDelete
    • scan0
    • class TikvIterator
• create another autotest in Jenkins and run integration tests on different branches of TiKV.
• run regression tests on every new minor/major version of TiKV.

[github-actions]

This issue is stale because it has been open 30 days with no activity.