Skip to content
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

[Feature Request] Option to disable tombstones in checkpoint files #3923

Open
2 of 8 tasks
felipepessoto opened this issue Dec 4, 2024 · 0 comments
Open
2 of 8 tasks
Labels
enhancement New feature or request

Comments

@felipepessoto
Copy link
Contributor

Feature request

Which Delta project/connector is this regarding?

  • Spark
  • Standalone
  • Flink
  • Kernel
  • Other (fill in here)

Overview

I'd like to confirm what is the current usage of tombstones in the checkpoint files. I couldn't find any references to it in the code.

If they are not used, I'd suggest having an option to don't include it in the checkpoint, since is some scenarios like when running MERGE command could rewrite all the files, and the checkpoint become huge and most of the data are tombstones.

Motivation

Tombstones are likely only wasting space and causing performance issues.

Willingness to contribute

The Delta Lake Community encourages new feature contributions. Would you or another member of your organization be willing to contribute an implementation of this feature?

  • Yes. I can contribute this feature independently.
  • Yes. I would be willing to contribute this feature with guidance from the Delta Lake community.
  • No. I cannot contribute this feature at this time.
@felipepessoto felipepessoto added the enhancement New feature or request label Dec 4, 2024
@felipepessoto felipepessoto changed the title [Feature Request] Tombstones in checkpoint [Feature Request] Option to disable tombstones in checkpoint files Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant