Array(Nested(...)) columns silently decode as Array(Nothing) and desynchronize the native block stream
維護者通常 4 天內回覆
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 68/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- clickhouse, cpp
研究方向
Start with clickhouse/types/type_parser.cpp, tracing GetTypeMeta(), ValidateAST(), and CreateColumnFromAst for the Array(Nested(...)) reproduction. Then inspect clickhouse/columns/factory.cpp and the ColumnNothing behavior described in columns/nothing.h. Add coverage for the expected nested type or explicit unsupported-type failure, and verify the pure client-side test no longer yields Array(Nothing).
由索引模型根據 Issue 內容生成。
描述
Description
The type parser has no entry for Nested, so a column whose server-reported type is Array(Nested(key String, value String)) is parsed as Array(<unknown terminal>) with Type::Void, and CreateTerminalColumn() maps Type::Void to ColumnNothing. The result is that CreateColumnByType() returns a perfectly valid-looking ColumnArray(ColumnNothing) — no error, no nullptr — and Client::Select() happily accepts it when reading the block header.
This matters because Nested inside Array(...) is not flattened by the server. Unlike a top-level Nested column (which the server splits into col.key Array(String), col.value Array(String) — the case discussed in #40), Array(Nested(...)) is reported over the native protocol with the literal type name:
$ clickhouse-client -q "SELECT name, type FROM system.columns WHERE table='some_data'"
id UInt64
data Array(Nested(key String, value String))
On the wire Array(Nested(k String, v String)) is serialized as Array(Array(Tuple(String, String))). But the client builds Array(Nothing), and ColumnNothing::LoadBody() (clickhouse/columns/nothing.h:61) just does input->Skip(rows) — 1 byte per element. So after reading the outer offsets the client skips N bytes where the server actually wrote 8*N inner-offset bytes plus all the string data. The input stream is desynchronized from that point on: the remaining block (and every block after it) is decoded as garbage, typically surfacing much later as an unrelated parse failure or a corrupted/empty result rather than a clear "unsupported type" error.
This is the C++ analogue of ClickHouse/clickhouse-java#3178, where the JDBC driver also failed on Array(Nested(...)) because its conversion layer did not account for Nested producing an extra list level.
Related but distinct from #40, which asks for a convenience API over flattened top-level Nested columns (those already work, since the server hands them over as plain Array(T)). Here the client receives a literal Nested(...) type name and silently produces wrong data.
ClickHouse server version
26.9.8.3 — used to confirm the type name the server reports for Array(Nested(...)) (shown above).
Code analysis only; the C++ repro below was written but not executed — binary execution was unavailable in the environment I investigated from. The static trace through TypeParser::Parse → CreateColumnFromAst → CreateTerminalColumn is given in full under "Suggested fix" below, and the first assertion (Array(Nothing)) is a pure parser/factory fact requiring no server.
Reproduction
Pure client-side, no server needed — this already demonstrates the root cause:
#include <clickhouse/columns/factory.h>
#include <gtest/gtest.h>
using namespace clickhouse;
TEST(CreateColumnByType, ArrayOfNested) {
auto col = CreateColumnByType("Array(Nested(key String, value String))");
ASSERT_NE(nullptr, col);
// Expected: Array(Array(Tuple(String, String)))
// Actual: Array(Nothing)
EXPECT_EQ("Array(Array(Tuple(String, String)))", col->Type()->GetName());
}
End-to-end, against a server:
CREATE TABLE some_data (
`id` UInt64,
`data` Array(Nested(`key` String, `value` String))
) ENGINE = Memory;
INSERT INTO some_data VALUES
(1, [[('key1','test'), ('key2','another-test')], [('key1','more-data')]]);
#include <clickhouse/client.h>
#include <iostream>
using namespace clickhouse;
int main() {
Client client(ClientOptions().SetHost("localhost").SetPort(9000));
client.Select("SELECT id, data FROM some_data", [](const Block& block) {
for (size_t c = 0; c < block.GetColumnCount(); ++c) {
std::cout << block.GetColumnName(c) << " -> "
<< block[c]->Type()->GetName() << "\n";
}
});
}
Expected: the data column comes back as Array(Array(Tuple(String, String))) with the two inner arrays intact (or, failing that, a clear UnimplementedError naming the unsupported type).
Actual: data is reported as Array(Nothing) carrying no values, and because ColumnNothing::LoadBody under-consumes the stream by the full size of the inner offsets and strings, decoding of the rest of the response is corrupted.
Suggested fix
Trace of the current behaviour:
clickhouse/types/type_parser.cpp:116—GetTypeMeta()has noNestedbranch, so theNested(...)node falls through toTypeAst::Terminal.clickhouse/types/type_parser.cpp:107—GetTypeCode("Nested")misseskTypeCodeand returnsType::Void.clickhouse/types/type_parser.cpp:152—ValidateAST()does reject unknownTerminal+Voidnodes, but it is only ever called on the root AST node (type_parser.cpp:238). The root here isArray, so the bad child is never validated.clickhouse/columns/factory.cpp:49—CreateTerminalColumn()mapsType::VoidtoColumnNothing, turning the unknown type into a silently-wrong column instead of anullptr.
Two things worth doing, independently useful:
-
Support
Nested.Nested(a T1, b T2)is exactlyArray(Tuple(a T1, b T2)). Adding aNestedmeta that desugars to that inCreateColumnFromAstwould makeArray(Nested(...))decode correctly, and would also let named-tuple element names (already supported viaTypeAst::element_name) carry through. -
Fail loudly on unknown nested types. Apply
ValidateASTrecursively, or haveCreateTerminalColumnreturnnullptrforType::Voidwhenast.nameis not literallyNothing/void. Right now any unrecognized type nested inside a container degrades toColumnNothingand desynchronizes the stream rather than raisingUnimplementedError. (Same silent-desync failure mode as #543.)
Link
Original client issue: https://github.com/ClickHouse/clickhouse-java/issues/3178
- 主要語言
- C
- 星號
- 386
- 分支
- 212
- 平均合併
- 4 天 20 小時
- 30 天內合併 PR
- 10
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
ClickHouse/clickhouse-cpp 的其他 Issue
-
enhancement pg_clickhouse
難度 2/5 1-3 小時 新手友好度 65/100
ClickHouse/clickhouse-cpp#478 · 1 則留言 ·
維護者通常 4 天內回覆
-
Homebrew support未關閉
難度 5/5 一週以上 新手友好度 25/100
ClickHouse/clickhouse-cpp#597 ·
維護者通常 4 天內回覆
-
難度 4/5 3-5 天 新手友好度 20/100
ClickHouse/clickhouse-cpp#596 ·
維護者通常 4 天內回覆
-
難度 3/5 1-2 天 新手友好度 35/100
ClickHouse/clickhouse-cpp#595 ·
維護者通常 4 天內回覆
-
Unknown type names inside a container are misread instead of rejected可能已有人在做 @Hakaou 於 15 天前認領。 未關閉
難度 4/5 1-2 天 新手友好度 48/100
ClickHouse/clickhouse-cpp#589 ·
維護者通常 4 天內回覆
查看 ClickHouse/clickhouse-cpp 的全部 Issue
相似的 Issue
-
examples/dnsdoctor: cleanup.sh stops at the first missing piece of a setup.sh that did not finish未關閉severity: low
難度 2/5 1-3 小時 新手友好度 70/100
luainkernel/lunatik#2263 ·
維護者通常 1 天內回覆
-
難度 2/5 半天 新手友好度 72/100
vercel-labs/scriptc#2910 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 68/100
darktable-org/darktable#22939 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 82/100
espressif/idf-extra-components#903 ·
維護者通常 1 天內回覆
-
os: input_password leaves terminal echo disabled when reading fails可能已有人在做 @davlgd 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆