Server should handle the case of table_id inconsistent between table node and partition node

[wuchong]

Search before asking

• I searched in the issues and found nothing similar.

Motivation

A follow-up of #766.

It seems it's hard to guarantee the consistency of table node and partition node. Even with #766, there is still possible happen a partition node is created by AutoPartitionManager under a re-created table node.

We need to handle this in server side for

1. ListPartition RPC: should filter out the partitions not match the table id
2. Metadata RPC: should filter our the partition metadata that not match the table id
3. CoordinatorEventProcess should handle CreatePartitionEvent that the partition is not match the table id and maybe drop the dirty partition node.

Solution

No response

Anything else?

No response

Willingness to contribute

• I'm willing to submit a PR!