Repository navigation
Stable 25.8 Backport of #93663 - Fix trash in TokenExtractor - #2672
Conversation
…rator Fix trash in `TokenExtractor` Conflicts committed as-is; the next commit resolves them: - src/Interpreters/ITokenExtractor.cpp (both modified)
|
Backporter: cherry-pick conflicts resolved by AI Conflicted files:
Commits:
|
|
Backporter: CI failures at 8148987 Failed checks: Needs a human: The conflict-resolution commit moved 58 contrib submodules to upstream versions, which breaks CMake; reverting them needs
|
Applied the buffer-length checks in stable-25.8's pointer style (`*pos`, `*token_length`) and dropped the `SparseGramsTokenExtractor` code, which doesn't exist on this branch.
8148987 to
60fc76c
Compare
Added explicit `ENGINE = MergeTree ORDER BY ()` to the table in 03784_msan_token_iterator, since stable-25.8 requires an ORDER BY / PRIMARY KEY by default
CI triage for
|
| Check | Verdict |
|---|---|
| Stateless tests (amd_binary, old analyzer, s3 storage, DatabaseReplicated, sequential): 1 failed / 579 passed | Flaky, not caused by this PR |
| DCO | Process issue: the commits have no Signed-off-by |
| PR (gate) | Roll-up of the above |
All other suites passed, including the new test 03784_msan_token_iterator everywhere it ran.
1. 01079_parallel_alter_detach_table_zookeeper (DatabaseReplicated, sequential)
The final cleanup DROP timed out on one of the 3 replicas:
Code: 159. DB::Exception: ReplicatedDatabase DDL task /test/clickhouse/db/test_qycfap0o/log/query-0000000020 is not finished on 1 of 3 hosts
(0 of them are currently executing the task, 0 are inactive). ... Was waiting for 120.615864638 seconds, which is longer than
distributed_ddl_task_timeout. (TIMEOUT_EXCEEDED) (query: DROP TABLE IF EXISTS concurrent_alter_detach_1)
The test's own stdout (1725 ×3, Starting/Finishing alters, 1/0 ×3) is correct. Only the timed-out DROP made it fail.
Why it's not this PR:
- The PR only touches
src/Interpreters/ITokenExtractor.cpp(token iteration used by text/bloom-filter indexes) and adds one new test. Neither has anything to do with ReplicatedDatabase DDL, ZooKeeper, or ALTER/DETACH. - This is a known upstream flaky test with the same failure mode (
DROP TABLE IF EXISTS concurrent_alter_detach_Nfailing in the same DatabaseReplicated job): Test 01079_parallel_alter_detach_table_zookeeper is flaky ClickHouse/ClickHouse#91413 and Flaky test: 01079_parallel_alter_detach_table_zookeeper ClickHouse/ClickHouse#97358. - Upstream fixed it in Fix flaky test
01079_parallel_alter_detach_table_zookeeperClickHouse/ClickHouse#96888 and Fix flaky test01079_parallel_alter_detach_table_zookeeperClickHouse/ClickHouse#97681 (26.2 timeframe). Neither is onstable-25.8; the last change to the test on this branch is Fix flaky test 03364_estimate_compression_ratio ClickHouse/ClickHouse#86003.
Next step: safe to re-run the job. If it keeps hitting stable-25.8 backports, backporting the test-only fixes ClickHouse#96888 and ClickHouse#97681 would stop it. That would be a separate PR, not this one.
2. DCO
Neither of the two commits added on top of the upstream merge has a Signed-off-by: trailer:
60fc76c7"Resolve conflicts in backport of Fix trash inTokenExtractorClickHouse/ClickHouse#93663"d61cddac"Fix CI failures (Fast test)"
The recently merged stable-25.8 backports I checked (#2694, #2692, #2639) don't report a DCO check at all, so it may not be enforced here. If it does have to be green, you'd need to sign off those commits, which means rewriting history and force-pushing. That's outside what I'm allowed to do, so it's up to you. Otherwise a maintainer can mark DCO as passed in the app.
Overall: no code fix is needed for this PR. Re-run the DatabaseReplicated stateless job and decide how to handle DCO.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
The usage of
ngram_bfindex on a non-UTF-8 data led to an uninitialized memory read, with values that could reside in the resulting index structure. Closes ClickHouse#92576. (ClickHouse#93663 by @alexey-milovidov)Documentation entry for user-facing changes
...
CI/CD Options
Exclude tests:
Regression jobs to run: