Skip to content

Detail the constraints in applying OPTIMIZE in Iceberg #25844

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

findinpath
Copy link
Contributor

@findinpath findinpath commented May 21, 2025

Description

Document the fact that partitions having
only one data file without any delete files
are disregarded for OPTIMIZE scenarios
in case of the Iceberg connector.

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

## Section
* Fix some things. ({issue}`issuenumber`)

@cla-bot cla-bot bot added the cla-signed label May 21, 2025
@findinpath findinpath requested a review from ebyhr May 21, 2025 10:20
@github-actions github-actions bot added the docs label May 21, 2025
@findinpath findinpath requested a review from raunaqmorarka May 21, 2025 10:20
Document the fact that partitions having
only one data file without any delete files
are disregarded for `OPTIMIZE` scenarios
in case of the Iceberg connector.
@findinpath findinpath force-pushed the findinpath/docs-OCiceberg-optimize branch from 1bea51a to 3a45cf4 Compare May 23, 2025 11:05
@findinpath findinpath requested a review from raunaqmorarka May 23, 2025 11:05
@raunaqmorarka raunaqmorarka requested a review from mosabua May 26, 2025 04:04
@raunaqmorarka raunaqmorarka merged commit 7f9f4ee into trinodb:master Jun 3, 2025
8 checks passed
@github-actions github-actions bot added this to the 476 milestone Jun 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants