tidb

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

Error 报告

This repository is ONLY used to solve problems related to DOCS-CN.
For other issues (TiDB, TiKV, etc), please move to other repositories.

Please answer the following questions before submitting your issue. Thanks!

Feature Request

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

The shared informer factory has called the WaitForCacheSync method, and it is no longer need to call it separately for each controller. We can remove Informer ().HasSynced because it will not be used.

See questdb/questdb#595.

In pingcap/docs#695 we determined that SQL keywords should be in all caps. There are a number of pages that require updating.

Is your feature request related to a problem?

For now, we have a bunch of make commands but no docs. It isn't easy to find the available commands.

Describe the feature you'd like

Adapt from https://www.thapaliya.com/en/writings/well-documented-makefiles/ and add help docs for each command.

Describe alternatives you've considered

No response

Teachability, Documen

Question

TiDB-Lightning doesn't need data to keep in order of _tidb_rowid, but we still sort data in the order of _tidb_rowid. This may increase TiDB's memory usage because we'll need a global sort in TiDB.

The flink-tidb-connector doesn't work as expected when I use upsert mode to sink data to TiDB, the reason for this is as in title, flink version: 1.13.x. Is there any reason for making unique key as part of the primary?

Code block:

private String[] getKeyFields(Context context, ReadableConfig config, String databaseName,
      String tableName) {
    // check write mode
    TiDBWr

Please answer these questions before submitting your issue. Thanks!

1. What did you do?
   If possible, provide a recipe for reproducing the error.
   we didn't record store id when download/ingest sst failed.

2. What did you expect to see?
   the error log with store id.

3. What did you see instead?
   only the error.

4. What version of BR and TiDB/TiKV/PD are you using?

all version.

The best practices of reporting errors:

1. The error message should be more user-friendly. Bad case: The table 101 exceeds table size. Good case: The table tbl exceeds table size.
2. Provide workarounds if necessary. Bad case: The table tbl exceeds table size. Good case: The table tbl exceeds table size. Please try to turn up the value of the system variable tmp_table_size.
3. Define