server: handle partitioned table in some http APIs

[tiancaiamao]

What problem does this PR solve?

mysql> create table xx (a int) partition by range (a) 
    -> (partition p0 values less than (255),
    -> partition p1 values less than (65535),
    -> partition p2 values less than (100000));
Query OK, 0 rows affected (0.16 sec)

Visit the HTTP API http://localhost:10080/tables/test/xx/regions

Before:

{
 "name": "xx",
 "id": 43,
 "record_regions": [
  {
   "region_id": 42,
   "leader": {
    "id": 43,
    "store_id": 1
   },
   "peers": [
    {
     "id": 43,
     "store_id": 1
    }
   ],
   "region_epoch": {
    "conf_ver": 1,
    "version": 21
   }
  }
 ],
 "indices": []
}

After:

[
 {
  "name": "p0",
  "id": 44,
  "record_regions": [
   {
    "region_id": 44,
    "leader": {
     "id": 45,
     "store_id": 1
    },
    "peers": [
     {
      "id": 45,
      "store_id": 1
     }
    ],
    "region_epoch": {
     "conf_ver": 1,
     "version": 22
    }
   }
  ],
  "indices": []
 },
 {
  "name": "p1",
  "id": 45,
  "record_regions": [
   {
    "region_id": 46,
    "leader": {
     "id": 47,
     "store_id": 1
    },
    "peers": [
     {
      "id": 47,
      "store_id": 1
     }
    ],
    "region_epoch": {
     "conf_ver": 1,
     "version": 23
    }
   }
  ],
  "indices": []
 },
 {
  "name": "p2",
  "id": 46,
  "record_regions": [
   {
    "region_id": 2,
    "leader": {
     "id": 3,
     "store_id": 1
    },
    "peers": [
     {
      "id": 3,
      "store_id": 1
     }
    ],
    "region_epoch": {
     "conf_ver": 1,
     "version": 23
    }
   }
  ],
  "indices": []
 }
]

And the HTTP API http://localhost:10080/regions/44

Before:

{
 "region_id": 44,
 "start_key": "dIAAAAAAAAAs",
 "end_key": "dIAAAAAAAAAt",
 "frames": null
}

After:

{
 "region_id": 44,
 "start_key": "dIAAAAAAAAAs",
 "end_key": "dIAAAAAAAAAt",
 "frames": [
  {
   "db_name": "test",
   "table_name": "xx(p0)",
   "table_id": 44,
   "is_record": true
  }
 ]
}

What is changed and how it works?

Now the following two http endpoint supports partitioned table:

• /tables/{db}/{table}/regions
• /regions/{regionID}

Check List

Tests

• Unit test
• Manual test (add detailed scripts or steps below)

Related changes

• Need to cherry-pick to the release branch

[tiancaiamao]

PTAL @jackysp @lysu

[tiancaiamao]

/run-all-tests

[lysu]

LGTM

[jackysp]

LGTM

[sre-bot]

/run-all-tests

[sre-bot]

@tiancaiamao merge failed.

[codecov]

Codecov Report

Merging #11463 into master will increase coverage by 0.184%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##             master     #11463       +/-   ##
===============================================
+ Coverage   81.3575%   81.5416%   +0.184%     
===============================================
  Files           424        424               
  Lines         90857      91736      +879     
===============================================
+ Hits          73919      74803      +884     
+ Misses        11623      11619        -4     
+ Partials       5315       5314        -1

[zz-jason]

/run-integration-common-test
/run-common-test

[sre-bot]

cherry pick to release-3.0 in PR #11466