steFaiz opened a new pull request, #8495: URL: https://github.com/apache/paimon/pull/8495
### Purpose Parts of https://github.com/apache/paimon/issues/8322 This PR introduce a new option to control whether to materialize deletions of a data evolution table. Why we don't always materialize deletions just like append tables? There are several reasons: 1. Materializing deletions will force compacting all columns including blobs at once(to keep row id alignment) 2. Materializing deletions will reassign row ids 3. Materializing deletions will force invalidating all global indices of influenced partitions ### Tests See `DataEvolutionDeletionVectorTest` for core-module tests See `DataEvolutionDeletionTestBase` for spark e2e tests -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
