tracking issue for refactoring the Table trait and related structures

[waynexia]

What type of enhancement is this?

Tech debt reduction

What does the enhancement do?

With table engine in datanode being replaced by region engine in #1869, we should also reconsider the Table abstraction. Generally speaking, the datanode (or region server) will no longer be aware of table -- it only sees and handles regions. And consequently, all the data access kind API (read, write, delete etc.) should be removed from Table. This makes the Table trait only in response of metadata, like retrieving table info or table schema.

This change will be shipped in the following parts:

• RFC document docs: rfc of refactoring table trait #2106
• Add route info into TableInfo feat: prepare for implementing considering partition key in the distributed planner #2000
• Implement the two tables under the information schema in the flavor of TableFactory
• Remove PartitionExec, which is used to serve DistTable's scan() method
• Adapt Region Server's region operation requests
• Adapt DataFusion's table source to the new datanode (region server)
• Refactor those *Adaptors and *Adapters style: merge adaptor and adapter #1665
• Replace the old Table trait with the new Table struct refactor(table): remove Table impl for system #2270

Implementation challenges

No response

[waynexia]

Close as completed

[tisonkun]

@waynexia @zhongzc But we still have the Table trait and Arc<dyn Table> in many places. Shall we continue on this direction?

[tisonkun]

I'm trying to drop the Table trait ...