-
Notifications
You must be signed in to change notification settings - Fork 6k
Closed
Closed
Copy link
Labels
affects-7.5This bug affects the 7.5.x(LTS) versions.This bug affects the 7.5.x(LTS) versions.affects-8.1This bug affects the 8.1.x(LTS) versions.This bug affects the 8.1.x(LTS) versions.affects-8.5This bug affects the 8.5.x(LTS) versions.This bug affects the 8.5.x(LTS) versions.component/pdseverity/majortype/bugThe issue is confirmed as a bug.The issue is confirmed as a bug.
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Tried to apply a placement policy to the special "meta" range using the ALTER RANGE statement as described in the TiDB documentation:
📄 https://docs.pingcap.com/tidb/stable/sql-statement-alter-range/
Example SQL:
ALTER RANGE meta SET PLACEMENT POLICY = 'my_policy';
2. What did you expect to see? (Required)
no error
3. What did you see instead (Required)
ERROR 8243 (HY000): "[PD:placement:ErrRuleContent]invalid rule content, start key should be encoded in table mode: insufficient bytes to decode value”
4. What is your TiDB version? (Required)
v7.5.1
v8.5.1
Metadata
Metadata
Assignees
Labels
affects-7.5This bug affects the 7.5.x(LTS) versions.This bug affects the 7.5.x(LTS) versions.affects-8.1This bug affects the 8.1.x(LTS) versions.This bug affects the 8.1.x(LTS) versions.affects-8.5This bug affects the 8.5.x(LTS) versions.This bug affects the 8.5.x(LTS) versions.component/pdseverity/majortype/bugThe issue is confirmed as a bug.The issue is confirmed as a bug.