Lei, HUANG

> What's the status of this tracking issue right now? Can we close it or keep it? @evenyag @v0y4g3r I think it's sufficient to close this tracking issue. The unresolved...

You will also need to refactor `common_insert::insert::build_create_expr_from_insertion`'s `insert_batches` argument to `InsertExpr`

> Maybe we can create another table implementation in frontend just for system table? The new table implementation act as a "fan-out" adapter to its designated tables, and loop through...

> +1 for this. This resolves #399 > > Using UDS still requires serialization and deserialization between two parts, which may affect our performance benchmark. We need to setup a...

Currently we cannot remove SQL parser logic from datanode completely, since some gRPC services directly pass SQL as a string from frontend to datanode. https://github.com/GreptimeTeam/greptimedb/blob/0d4c191a06418b046ecae9337a173c59ad45a43f/src/datanode/src/instance/grpc.rs#L192 If we want to remove...

Thoughts on migrating the "auto-create/alter-on-insertion" feature from datanode to frontend: - "auto-create/alter-on-insertion" is a protocol-related feature that generally used in opentsdb and prometheus, so it's natural to move this feature...

In #455, we built a set of `handle_xxx` API for protocols, protocol handlers should not be aware of gRPC client directly (like `instance.admin()`.`instance.dataabse()`), instead, they convert requests from different protocols...

I just found that tests inside [`src/datanode/src/tests/instance_test.rs`](https://github.com/GrepTimeTeam/greptimedb/blob/22ae983280a4ea1f6b3a3ba0539466058018fbbc/src/datanode/src/tests/instance_test.rs) should also be moved to test-integration module.

> @v0y4g3r I checked that module and it seems for testing datanode only? Correct me if I'm wrong. That's right.

Same problem here, resize/move commands hang for seconds on Chrome. "AXEnhancedUserInterface was enabled, will disable before resizing" also appears in logs. Any workaround?