best-practices: add a new guide on mastering partitioned tables (#21846) #42753
ti-chi-botAnnotations
4 errors and 4 warnings
|
vale:
best-practices/tidb-partitioned-tables-best-practices.md#L726
[vale] reported by reviewdog 🐶
[PingCAP.Units] Put a nonbreaking space between the number and the unit in '2h'.
Raw Output:
{"message": "[PingCAP.Units] Put a nonbreaking space between the number and the unit in '2h'.", "location": {"path": "best-practices/tidb-partitioned-tables-best-practices.md", "range": {"start": {"line": 726, "column": 72}}}, "severity": "ERROR"}
|
|
vale:
best-practices/tidb-partitioned-tables-best-practices.md#L725
[vale] reported by reviewdog 🐶
[PingCAP.Units] Put a nonbreaking space between the number and the unit in '2h'.
Raw Output:
{"message": "[PingCAP.Units] Put a nonbreaking space between the number and the unit in '2h'.", "location": {"path": "best-practices/tidb-partitioned-tables-best-practices.md", "range": {"start": {"line": 725, "column": 72}}}, "severity": "ERROR"}
|
|
vale:
best-practices/tidb-partitioned-tables-best-practices.md#L724
[vale] reported by reviewdog 🐶
[PingCAP.Units] Put a nonbreaking space between the number and the unit in '59s'.
Raw Output:
{"message": "[PingCAP.Units] Put a nonbreaking space between the number and the unit in '59s'.", "location": {"path": "best-practices/tidb-partitioned-tables-best-practices.md", "range": {"start": {"line": 724, "column": 80}}}, "severity": "ERROR"}
|
|
vale:
best-practices/tidb-partitioned-tables-best-practices.md#L723
[vale] reported by reviewdog 🐶
[PingCAP.Units] Put a nonbreaking space between the number and the unit in '42s'.
Raw Output:
{"message": "[PingCAP.Units] Put a nonbreaking space between the number and the unit in '42s'.", "location": {"path": "best-practices/tidb-partitioned-tables-best-practices.md", "range": {"start": {"line": 723, "column": 81}}}, "severity": "ERROR"}
|
|
vale:
best-practices/tidb-partitioned-tables-best-practices.md#L462
[vale] reported by reviewdog 🐶
[PingCAP.Ambiguous] Consider using a clearer word than 'sufficient' because it may cause confusion.
Raw Output:
{"message": "[PingCAP.Ambiguous] Consider using a clearer word than 'sufficient' because it may cause confusion.", "location": {"path": "best-practices/tidb-partitioned-tables-best-practices.md", "range": {"start": {"line": 462, "column": 94}}}, "severity": "INFO"}
|
|
vale:
best-practices/tidb-partitioned-tables-best-practices.md#L236
[vale] reported by reviewdog 🐶
[PingCAP.Ambiguous] Consider using a clearer word than 'much' because it may cause confusion.
Raw Output:
{"message": "[PingCAP.Ambiguous] Consider using a clearer word than 'much' because it may cause confusion.", "location": {"path": "best-practices/tidb-partitioned-tables-best-practices.md", "range": {"start": {"line": 236, "column": 99}}}, "severity": "INFO"}
|
|
vale:
best-practices/tidb-partitioned-tables-best-practices.md#L226
[vale] reported by reviewdog 🐶
[PingCAP.Ambiguous] Consider using a clearer word than 'a large number of' because it may cause confusion.
Raw Output:
{"message": "[PingCAP.Ambiguous] Consider using a clearer word than 'a large number of' because it may cause confusion.", "location": {"path": "best-practices/tidb-partitioned-tables-best-practices.md", "range": {"start": {"line": 226, "column": 102}}}, "severity": "INFO"}
|
|
vale:
best-practices/tidb-partitioned-tables-best-practices.md#L123
[vale] reported by reviewdog 🐶
[PingCAP.Ambiguous] Consider using a clearer word than 'many' because it may cause confusion.
Raw Output:
{"message": "[PingCAP.Ambiguous] Consider using a clearer word than 'many' because it may cause confusion.", "location": {"path": "best-practices/tidb-partitioned-tables-best-practices.md", "range": {"start": {"line": 123, "column": 117}}}, "severity": "INFO"}
|