Altinity / Altinity/clickhouse-regression
Failure: /iceberg/iceberg engine/rest catalog/show_data_lake_catalogs hint — empty SHOW TABLES on non-Antalya and <26.1 CI
@CarlosFelipeOR is already working on this.
Since Apr 8, 2026.
- Dominant language
- Python
- Stars
- 27
- Forks
- 10
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Description
Affected tests
/iceberg/iceberg engine/rest catalog/show_data_lake_catalogs hint/*
Affected files
iceberg/tests/iceberg_engine/show_data_lake_catalogs_repro.pyiceberg/regression.py
Summary
The similar_table_names_hint scenario expects that, with show_data_lake_catalogs_in_system_tables = 0, tables stay out of system.tables but SHOW TABLES FROM still lists names like schema1.table. On non-Antalya builds and ClickHouse < 26.1, SHOW TABLES FROM returned empty output, so assertions such as assert f"{namespace}.{table_name}" in result.output failed in CI.
Description
The scenario was added on 2026-03-27 in 8d10a5bcc (Add new test for show_data_lake_catalogs hint behavior). After that, Iceberg CI on binaries other than Antalya 26.1+ began failing on this subtree: system.tables behaved as expected (no catalog tables), but SHOW TABLES FROM produced no rows in the client output.
Analysis
Root cause
The behavior under test comes from Antalya 26.1 work on DataLakeCatalog and UNKNOWN_TABLE / typo hints when show_data_lake_catalogs_in_system_tables is disabled—Altinity/ClickHouse#1583 (backport of ClickHouse/ClickHouse#100452).
Follow-up (when upstream lands)
After ClickHouse#100452 merges and the behavior exists in a known upstream version, revisit the skip in iceberg/regression.py: tighten check_clickhouse_version and drop check_if_not_antalya_build() if it is no longer required.
Resolution
Skip this subtree unless Antalya and ClickHouse ≥ 26.1:
- 9ab8a01 — Skip show_data_lake_catalogs hint tests outside Antalya 26.1+
References
- Test introduction: 8d10a5bcc
- Antalya backport: Altinity/ClickHouse#1583
- Upstream PR: ClickHouse/ClickHouse#100452
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.
Assessment
This issue has not been assessed yet.