do we need include the plan of databend-operator in this checklist? it's in a stand-alone repository

do we need include the plan of databend-operator in this checklist? it's in a stand-alone repository

I think so, we should add at least two things:

1. refactor databend-operator for meta service and DAL storage
2. add test infra to test databend-operator on different cloud providers( AWS, GKE etc)

it would be nice to have the following experimental features:

1. monitoring demo(add prometheus to databend_cluster)
2. Autoscaling with keda
3. multi-cluster scheduling with admiralty or karmada etc.

Plus, we should also support bendctl integration with operator for basic logging, debugging and visualization supports

Besides in CI and e2e test part, we should add the following tests to guarantee our OOS quality.

1. regular stateful test for local and Object storage(mocking)
2. Test kubernetes operator integration part and demo part before release get published during stable channel release.
3. Periodically test the kubernetes operator and helm part reside in different providers and clusters (perhaps once a day)

Not sure about when would us ready to run TPC-H benchmarks on large cluster, but we could prepare it on test infra.

1. Cluster size and estimated cost plan
2. test infra CI scripts to run TPC-H on GKE or graviton EKS
3. TPC-H dataset preparation and query part

adding a system.columns table with a SHOW COLUMNS table syntax: #2608

HTTP API with polling based incremental body response & progress metadata

a new databend-playground with a modern SQL IDE

Update metasrv tasks

Add Experimental checklist:

• User grant privileges #2679

@BohuTANG

HTTP handler API works with all the queries which databend support(need issue)

It seems no extra work is required to support "all the queries".

So I only need to add tests for each interpreter?

By the way, why insert result is "0 rows affected" now?

@BohuTANG

HTTP handler API works with all the queries which databend support(need issue)

It seems no extra work is required to support "all the queries".

So I only need to add tests for each interpreter?

Ok.

By the way, why insert result is "0 rows affected" now?

I guess there is something wrong with the status(http handler), we could check it from the MySQL client.

Progress report:

• Document Loading Data into Databend #3181
• Document http handler api #3143

Once these two issues are finshed, we are ready to release v0.6 🚀

Note
Other unfinished tasks will be rolled to the next version(Nightly v0.7)

This release is ready and will be released as scheduled 🚀