Issue on docs

Open Beginner friendly

#4,066 opened on Aug 17, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 68/100

Issue type: Documentation
Clarity: Mostly clear
Activity status: Active
Tech stack: sql
Domain: databases, documentation

Research direction

Open /zh-CN/docs/3.x/data-operate/update/unique-update-concurrent-control and review the two quoted passages together, checking the surrounding sequence-column documentation. Verify whether the DDL setting is sequence_col or sequence_type and whether imports must explicitly map the sequence column. Done means the terminology is corrected and the two statements consistently describe the documented behavior.

Written by the indexing model from the issue text.

Description

Path:/zh-CN/docs/3.x/data-operate/update/unique-update-concurrent-control

"如果建表时使用了 function_column.sequence_col 方式来指定 sequence 列，在导入时需要指定 sequence 列到其他列的映射。"
应该改为
“如果建表时使用了 function_column. sequence_type 方式来指定 sequence 列，在导入时需要指定 sequence 列到其他列的映射。“

"为防止误用，在 StreamLoad/BrokerLoad 等导入任务以及行更新 insert 语句中，用户必须显示指定 sequence 列 (除非 sequence 列的默认值为 CURRENT_TIMESTAMP)，不然会收到以下报错信息："
这句话与前面的描述冲突。当用户在DDL中已经通过function_column.sequence_col指定了sequence列之后，后续的导入似乎并不需要指定sequenct列？

Dominant language: MDX
Stars: 134
Forks: 466
Avg merge: 1d 11h
Merged PRs (30d): 54

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Batched `completeJobs`/`failJobs` are never retried: the retry loop in `batch()` exits after the first failure Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

graphile/worker#636 · Opened Sep 21, 2026
Test Failure: com.ibm.ws.jdbc.fat.sqlserver.SQLServerTest J2CA0079E Open

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

OpenLiberty/open-liberty#35839 · Opened Sep 21, 2026
hash join v2: 'unsupported column type for pre-alloc 225' when joining on a VECTOR column Open

affects-9.0 found-by-ai may-affects-25.10 may-affects-26.3 may-affects-26.9 may-affects-7.5 may-affects-8.1 may-affects-8.5 severity/major sig/execution type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

pingcap/tidb#71473 · Opened Sep 21, 2026
JSON_VALUE fails to parse when a RETURNING clause is present but the optional ON EMPTY/ON ERROR clause is omitted Open

Difficulty 1/5 Under an hour Newbie friendliness 92/100

antlr/grammars-v4#5014 · 1 comment · Opened Sep 21, 2026
readBinary(std::vector) throws a bare Poco::Exception (POCO_EXCEPTION code 1000) for too-large sizes instead of TOO_LARGE_ARRAY_SIZE Open

comp-query-execution fuzz

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

ClickHouse/ClickHouse#121303 · 3 comments · Opened Sep 21, 2026

More Databases issues