Skip to content

Antalya 26.6: Change the interface for Iceberg inserts with the catalog - #2149

Open
zvonand wants to merge 2 commits into
antalya-26.6from
feature/antalya-26.6/pr-1800
Open

Antalya 26.6: Change the interface for Iceberg inserts with the catalog#2149
zvonand wants to merge 2 commits into
antalya-26.6from
feature/antalya-26.6/pr-1800

Conversation

@zvonand

@zvonand zvonand commented Aug 3, 2026

Copy link
Copy Markdown
Member

Changelog category (leave one):

  • Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Change the interface for Iceberg inserts with the catalog.
Deprecate settings: storage_catalog_type, storage_aws_access_key_id, etc (ClickHouse#100334 by @scanhex12).

Cherry-picked from ClickHouse#100334.

--- (#1800 by @zvonand).

Cherry-picked from #1800.


Documentation entry for user-facing changes

  • Documentation is written (mandatory for new features)

zvonand added 2 commits August 3, 2026 15:36
…next commit)

---
Original cherry-pick message follows:

Merge pull request #1800 from Altinity/feature/antalya-26.3/ClickHouse-ClickHouse-pr-100334

Antalya 26.3: Change the interface for Iceberg inserts with the catalog
# Conflicts:
#	src/Databases/DataLake/DatabaseDataLake.cpp
#	src/Storages/ObjectStorage/DataLakes/DataLakeConfiguration.h
#	src/TableFunctions/TableFunctionObjectStorage.cpp
#	tests/integration/test_database_glue/test.py
#	tests/integration/test_database_iceberg/test.py
antalya-26.6 already carries the equivalent of every change in #1800 (public DatabaseDataLake::getCatalog, getCatalog(ContextPtr, const StorageID &) signature, the DatabaseCatalog-based catalog lookup with the deprecated-settings check, no catalog passed from table functions, and the settings= kwargs form in the integration tests), so each conflict hunk is pure base-branch divergence and 'ours' is kept: lazy initialize()/getCatalog split in DatabaseDataLake, StorageObjectStorageCluster ctor arity in TableFunctionObjectStorage, the StorageIcebergConfiguration block and minio1:9001 / DataLakeCatalog / eager 'Unspecified catalog type' expectations in the tests.
@zvonand zvonand added releasy Created/managed by RelEasy antalya-26.6 ai-resolved Port conflict auto-resolved by Claude labels Aug 3, 2026
@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown

Workflow [PR], commit [defffb4]

@zvonand zvonand added the forwardport This is a frontport of code that existed in previous Antalya versions label Aug 4, 2026
@ianton-ru

Copy link
Copy Markdown

Is it possible to run integration tests for this pr? It is possible that need to add also changes from #1842

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai-resolved Port conflict auto-resolved by Claude antalya-26.6 forwardport This is a frontport of code that existed in previous Antalya versions releasy Created/managed by RelEasy

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants