scale

Enhancement

mysql> CREATE TABLE t1 (
    -> risk_id varchar(32) NOT NULL,
    -> tran_id int NOT NULL,
    -> KEY (`risk_id`)
    -> );

mysql> CREATE TABLE t2 (
    -> risk_id varchar(32) COLLATE utf8mb4_general_ci NOT NULL,
    -> -- risk_id varchar(32) NOT NULL,
    -> tran_id int NOT NULL,
    -> KEY (`risk_id`)
    -> );

mysql> explain select /*+ hash_join(t1) */ t1.ris

/area API
/area autoscale
/kind cleanup

Actual Behavior

The max-scale and min-scale annotation has been introduced in knative/serving#12103 alignment. The client was using those names, but recently this changed to the inverse - knative/client#958. This leads to confusion on docs, and UX as seen in: https://github.com/knative/docs/iss

Describe your question

平台：mac m1 arm64
容器平台： docker desktop V4.5.0
docker版本：Server Version: 20.10.12 Storage Driver: overlay2
运行镜像：oceanbase/oceanbase-ce standalone-3.1.3
启动命令：docker run -p 2881:2881 --name obstandalone --platform linux/amd64 -e MINI_MODE=1 -d oceanbase/oceanbase-ce:standalone-3.1.3

启动过程中的问题：
启动执行 docker logs obstandalone 有以下信息

generate boot.yaml ...
/root/boot

Describe the bug

As it stands, users wishing to enable CloudWatch logs will need to go through the AWS Process to do so here and then manually modify the fluent-bit-config configmap to alter the generated log stream to match what Flyte expects.

kubectl edit cm -n amazo

As someone with little experience with Brighter, setting up a pipeline correctly can be a little tricky. For example, it's easy to mistakenly mix sync and async handlers, subscriptions, policies, etc. When building a consumer, Brighter informs me of these issues when I start everything up and send a message to my broker for my application to consume.

Is it possible to implement something that f

Is your feature request related to a problem? Please describe.

Updating escalator config currently requires a pod restart. We should update escalator to automatically read new config upon changing on disk.

Describe the solution you'd like

Check for changes in nodegroup config before each run. If safe to do so, run with the new config.

*Describe alternatives you've considered