feature (iceberg): Implement TRUNCATE TABLE for Iceberg Engine (REST …#1655
feature (iceberg): Implement TRUNCATE TABLE for Iceberg Engine (REST …#1655il9ue wants to merge 1 commit intoantalya-26.3from
Conversation
…catalog support) Forward-port of Iceberg TRUNCATE TABLE from antalya-26.1 to antalya-26.3. Adapted to antalya-26.3 API changes in RestCatalog constructor, DatabaseDataLakeSetting, and related interfaces. See original implementation details in antalya-26.1 PR #1529. Signed-off-by: Daniel Q. Kim <daniel.kim@altinity.com>
db43b6b to
e229240
Compare
On CI Failures & Asking a reviewFlagging the CI failures for review. All observed failures are pre-existing and unrelated to the Iceberg TRUNCATE changes in this PR.
Docker CVEs (CVE-2026-28388, CVE-2026-28389, CVE-2026-28390, CVE-2026-31790, CVE-2026-40200)
These require a base image update by the Docker/infra team and are unrelated to any C++ code changes in this PR. The same CVEs appear on the base This PR is a forward-port of the Iceberg TRUNCATE TABLE feature from |
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Frontport for Antalya 26.3
Adaptation notes for antalya-26.3
The following API changes between antalya-26.1 and antalya-26.3 required adaptation:
RestCatalogconstructor signature updated to matchantalya-26.3calling convention inDataLakeConfiguration.hDatabaseDataLakeSettingmember names updatedCargo.lockrestored toantalya-26.3version (our changes do not touch any Rust code)All feature logic is identical to the merged antalya-26.1 implementation.
CI/CD Options
Exclude tests:
Regression jobs to run: